- 1 year
Should ≠ Needs to
You can do it, and it will work, but it’s unclean and not best-practice. I wouldn’t be surprised if it’s undefined behaviour.
- 1 year
Just to clarify. It is defined behavior - there’s plenty of undefined behavior in C but that ain’t one of them.
Interesting feature, I had no idea. I just verified this with gcc and indeed the return register is always set to 0 before returning unless otherwise specified.
spoiler
int main(void) { int foo = 10; }produces:
push %rbp mov %rsp,%rbp movl $0xa,-0x4(%rbp) # Move 10 to stack variable mov $0x0,%eax # Return 0 pop %rbp retint main(void) { int foo = 10; return foo; }produces:
push %rbp mov %rsp,%rbp movl $0xa,-0x4(%rbp) # Move 10 to stack variable mov -0x4(%rbp),%eax # Return foo pop %rbp ret
- 1 year
should have a space after „>” and two new lines after „?”.
I guess markdown is miserable as well.
- kboy101222@sh.itjust.worksEnglish1 year
Hey now, markdown serves it’s purpose. It’s not great, but as a web dev, I don’t want people expecting full WYSIWYG editors in every website cause fuck that!
not being able to master markdown might hint at why the commenter is struggling with C++
Didn’t you know that C++ programmers are better than compilers at checking code for safety though? And if they aren’t, it’s a skill issue.
/s
And sensible compile times.
I’m trying to write a game in Bevy but my laptop’s Intel 7400 taking almost a minute to compile even small changes is really killing me.
I’ve looked up rustc compile times on different CPUs and am seriously considering getting a new laptop with a Snapdragon X Elite or something in that vein for this.
