News for hackers. Stuff that matters.
Re:QUIC is now RFC 9000 by anyfoo on Thursday May 27, 2021 @11:41PM (#27311490)
It's in a lot of ways more about not being defined (but possibly declared) yet, rather than initialized. You'd be super sad if you could not reference a function defined later in a source file.

Yeah, I'm absolutely great at parties!

Re:QUIC is now RFC 9000 by infogulch on Thursday May 27, 2021 @11:51PM (#27311548)
Ok, that explanation works for me. And if there was ever an appropriate time to be pedantic it would be in a discussion on RFCs. :)
Re:QUIC is now RFC 9000 by capableweb on Friday May 28, 2021 @08:08AM (#27314403)
> You'd be super sad if you could not reference a function defined later in a source file.

Would you? Most of the environments I'm in requires you to define the thing before you can use it, I'm not that sad about that. In fact, that seems to make a lot more sense than that you can define something after you use it, I'd expect that to lead to a compiler/interpreter error.

Re:QUIC is now RFC 9000 by jopsen on Friday May 28, 2021 @08:25AM (#27314532)
So no recursion?
Re:QUIC is now RFC 9000 by salawat on Friday May 28, 2021 @01:08PM (#27317930)
You totally can.

Remember, it's all about tokenizing. You're associating chunks of machine code to tokens that tell the machine where to go to get the actual definition, or where to plop the machine code if statically linking.

Nobody said that RFC numbering implied any sort of temporal order. You are the Linker. Be the Linker.

Re:QUIC is now RFC 9000 by capableweb on Friday May 28, 2021 @12:36PM (#27317503)
Depends on the compiler/interpreter. Function body could be parsed/evaled after the initial function definition.
Re:QUIC is now RFC 9000 by anyfoo on Friday May 28, 2021 @12:37PM (#27317510)
What environments are those?
Re:QUIC is now RFC 9000 by dzamo_norton on Sunday May 30, 2021 @05:21AM (#27331842)
E.g. Python