4 ms·
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 functio
by anyfoo 5y ago
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!
- infogulch 5y agoOk, that explanation works for me. And if there was ever an appropriate time to be pedantic it would be in a discussion on RFCs. :)
- capableweb 5y ago> 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.
- jopsen 5y agoSo no recursion?
- capableweb 5y agoDepends on the compiler/interpreter. Function body could be parsed/evaled after the initial function definition.
- salawat 5y agoYou 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.
- anyfoo 5y agoWhat environments are those?
- dzamo_norton 5y agoE.g. Python