> But they don't have the same meanings. LOAD happens at run-time, and thus, > it is impossible for a compiler to reason about the code being loaded at > compile time.
We seem to have a disagreement about the meaning of "meaning." To me, "meaning" means "what a program /means/" -- what the programmer intends. /Not/ what optimizations a compiler can or cannot do. Those things are called "optimization," which is entirely separate from "meaning." If you find that too vague to be useful, I propose as an alternative, "the meaning of a program is the string of characters that will be printed when that program is typed into an R4RS-compliant REPL." I choose R4RS because it doesn't talk about macros, and the macrology discussions on this list have convinced me that R5RS macros have no coherent meaning at all, since eminent macrologists can't agree about it. But please don't pick at the details of this paragraph, which I agree has holes in it; it's just a sop to people for whom the programmer's intent is too handwavy to be admissible; you can construct your own axiomatization of it. And I repeat (ad nauseam if necessary) that no word suffixed with "-time" is admissible in a discussion of WG1 Scheme, except for "REPL-time," which is admissible solely as a rhetorical counter to those other -times. :-) _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
