aaaa12345
I have some recommendations. All of them are kdramas and doesn't focus on romace.If you want to watch something about school life, I think Cheer Up!
(2015) is a good kdrama. Knows from name Sassy Go Go, too, this drama talks a lot about how education system in South Korea is tough. Plot happens in a high school where your grades is more important than your hobbies, talents and individuality.
Everyone has as goal be a top student with higher grades and all those whom don't do that are ignored by others. Most of top students has a toxic relationship with their parents and do everything to get a u201chigher ground". If you want something a little bit serious about adult life, I recommend Because This Is My First Life (2017).
I will ignore all plot in synopsis to tell you this drama talks about women in south korean society. We have 3 women in her 30s whom have great dreams but real life comes to separeted them from it. All the world is against them, what is horribly real.
They have problems with selfsteem, sexism in workplace, patriarchal families, pressure to marry and became a housewife and, at least, sexual assault. All these topics are really discussed throughtout drama (I cried in some episodes). If you want something about workplace, I recommend Radiant Office (2017).
Talks about 3 unemployed adults trying to commite suicide because they are always rejected in job interviews and exams, don't matter how dedicated they are. When they finally get a trainee experience, they will try to survive in a toxic workplace where just one of them will get a permanent job. If you want something about life and death, Hi Bye Mama (2020) will be your guest.
Responsible for some crying spells, our female lead is dead. She died giving birth her child and now is a ghost arounding her husband, daughter, friends and family. The most emotional scenes show how people dealt with her death, from the moment they received this notice until now, when they are trying to continue living.
We can watch too how some ghosts died, I mean, how their lives were suddenly interrupted and their biggest regrets
· Suggested Reading
How do I print a character multiple times in the assembly language?
Assuming you are talking about x86 assembly, printing could look like this:segment .data ; declare needed data in this section char db "a" ;Our caharacter, 'char' is the name, not a data type!
segment .text ;code section global main main: ;main progrsm, to write our string to stdout mov edx,1 ;third argument: message length mov ecx,char ;second argument: pointer to message to write mov ebx,1 ;first argument: file handle (stdout) mov eax,4 ;system call number (sys_write) mov ebp,5 ;bad idea, but 'enter' or EBP was not used otherwise, so safe hereprintloop: push eax ;EAX is modified by the sys call int 0x80 ;call kernel: "sys_write to STDOUT 1 characters of the string 'char'" pop eax ;if other regs are modded too, use PUSHA/POPA instead DEC ebp ;ebp-1 JNZ printloop ;if(ebp!0)->printloop;exit: xor eax,eax ;eax0 retIf you are talking of x64 assembly, the above code might still work somehow (it does on my machine!
) but the real way to do it looks like this:segment . data char db "a" ;Our caharactersegment .text ;section declaration global mainmain: mov rcx, 5 ; init jump count mov rdx,1 ;message length mov rsi,char ;pointer to message to write mov rdi,1 ;file handle (stdout) mov rax,1 ;system call number (sys_write) printloop: push rcx push r11 syscall pop r11 pop rcx loop printloop ;ECX-1, if(ECX!
0)->printloop;exit: xor eax,eax retSee ASM Tutorial for some basic stuff.Also, be careful with using EBP for counting stuff like I did in the x86 code. It does not matter in this example and made sense to use the here unused register instead of using the stack for a u2018local variableu2019 or a label defined in the data section, but using EBP for other than as the stack base is discouraged usually.
Also one would most likely create a print function with arguments delivered via the stack. However all that would have a toll on the performance, so I decided for this version instead. Note: Those system calls are for Linux.
If you want to compile for Windows or Mac, use the functions available at u2018asm_io.incu2019, see Using Libraries and nasm-asm_io-overview.pdf on the use of it
------
How do I add two numbers in assembly language?
It all depends on:The CPU architecture youu2019re targeting, because each CPU family has its own set of mnemonic assembly language instructions, addressing modes, etc.The data types you are attempting to add:If youu2019re adding integers, you may need to add two bytes, two 16-bit values, two 32-bit values, two 64-bit values, etc. Or you might be mixing an matching (e.
g., adding a byte to a 32-bit integer, etc.).
You might also be treating those values and the result as signed or unsigned values. If youu2019re adding floating-point (real number) values, you may need to add two 16-bit values, two 32-bit values, two 64-bit values, etc.If your hardware supports floating-point instructions, youu2019d use those instructions.
If your hardware doesnu2019t support floating-point instructions, then you have to provide (or call) assembly code that emulates floating-point addition in software. That said, the sequence of assembly instructions might be outlined by the following steps:Load the first operand from memory into a register.Load the second operand from memory into a register.
Perform an addition instruction between the two registers, leaving the result of the addition in a specific register. Of course, if you happen to already have one or both of the operands in registers (from previous operations), then you donu2019t have to load them from memory. Itu2019s also possible that your operands are not sitting somewhere in memory, but are constant values.
Some CPUs provide instructions that embed the constant directly into the instruction, so there is no need to explicitly load it from elsewhere in memory as a separate step. Some CPUs allow you to perform addition of two memory operands directly, without having to explicitly load them into registers. And some hardware is stack-based, where you place the two operands on a stack, perform an add operation, and leave the result of the add on the stack.
If you really want to know how to add two numbers in assembly language, you need to first figure out what CPU architecture youu2019re talking about, and what data types youu2019re working with. Only then could you begin to select the appropriate assembly language instructions
------
How will programming for quantum computing be different than programming for traditional computers?
If we regress programming classical computers to the level we are at now with quantum computers: providing an ordered list of instructions for the processor to carry out on the set of bits/qubits.
Classical computer programming is eventually compiled down to this level.Considering it at this level, there really is very little difference between quantum and classical programming. The only difference would be in the sets of possible instructions, with the quantum instructions being defined to also act on superposition states.
This may change as quantum computing advances and consequently so does the programming languages we use for them. At this point, I dont know what a quantum programming language would look like but I think we can say somethings about where it would diverge from classical languages:1) The language would have to be less focused on assigning values to variables. The exponential scaling of Hilbert spaces would make specifying a particular value too long, instead youd have to provide a series of steps to build the required state from a simple product state.
2) In a lot of cases, you dont want to always be using a quantum computer, so a classical computing language would have to be built in to handle the cases where quantum offers no/little advantage. So a quantum programming language would have to intrinsically consider parallelism between the quantum and classical processes.3) Reading the value of a quantum state collapses the superposition, so after reading the value of a quantum variable you have to accept that its value has now changed and not in a perfectly predictable way.
The days of printing variables out while debugging would be gone as measuring a variable now changes the logic of the program.4) The no cloning theorem would have a lot of effects. You can no longer just copy the value of a variable.
Wouldnt be a part of the language but something youd have to be aware of and something that a would throw an error in compilation. Would also have implications youd have to consider when using loops acting on the same variable. If you read it, it changes and you cant copy it.
------
Which language should I learn after C?
Wait, you know C!?
All of it? That's amazing!I'm teasing a little bit; there are very few people who know the depths of C.
I'm still learning useful new things regularly. So here's a quick quiz. The more of these you can answer, the better your C:What are some good practices to avoiding leaking memory?
What is the rule of 3? How has that rule changed in C11?Why can you add strings using s"y" and "x"s, but not "x""y"?
What is an output iterator and why do you need one?When is
How do you specify the template parameters when the compiler is unable to infer them from the templated function's arguments?What is the construction order for global variables when their constructor references other global variables?When you declare a class constant in a header file, does each compilation unit get its own copy of the constant?
Is friendship inherited by child classes?When are static local variables constructed?When is catch( .
) a security risk?What can pointers do that references can't do?Why can't you pass an inline value constructor into a function that takes a mutable reference as a parameter?
What is a cast operator and how do you write one?What is a functor and what are they good for?Why would you put something into an anonymous (nameless) namespace?
Which class member functions have default implementations, and what do those defaults do?Why would you make a destructor virtual? When should you not?
Under what conditions might a b; and a a b; give different results? If you can answer 15 of these, then I think you are pretty good at C. Otherwise, don't just drop it and move on; there is so much more depth to the language, and you will be far more productive when you have explored it.
Perhaps your next language should be the rest of C.That said, there are some good languages to complement C skills. You may wish to learn Lua.
It is wonderful for quickly embedding a script language inside of your C applications. You would be wise to learn a script language like Python, as C is a bit verbose for quick scripting tasks. Knowing a little JavaScript is essential if your software needs to talk to web browsers.
You should learn SQL if you need to work with databases. And you should learn just a little bit of InterCAL, so that you will have funny stories to tell when you meet other programmers.