Re: IMCC .globalconst?

2003-09-21 Thread Leopold Toetsch
Gregor N. Purdy [EMAIL PROTECTED] wrote: Leo -- I think the collection path is A Bad Idea (TM) for a language with scripting style (like Jako, Perl, Python, etc.). Symbol mangling is always up to the HLL. The PASM and PIR compilers don't care. The HLL has to emit symbol names that are

IMCC .globalconst?

2003-09-20 Thread Gregor N. Purdy
All -- I don't understand how .globalconst fits in with the IMCC policy of everything being in a .sub. The Jako compiler emits stuff like this right now (in my sandbox). It used to emit the constants as .const right where the were found lexically, but I've introduced code motion to collect all

Re: IMCC .globalconst?

2003-09-20 Thread Leopold Toetsch
Gregor N. Purdy [EMAIL PROTECTED] wrote: All -- It used to emit the constants as .const right where the were found lexically, but I've introduced code motion to collect all inline code into the __MAIN sub at the end, which put the .const stuff there (which I've changed to .globalconst in the

Re: IMCC .globalconst?

2003-09-20 Thread Gregor N. Purdy
Leo -- I'm going to chuck the idea of collecting stuff, and use this: .sub _INLINE_{N} # a chunk of stuff goto _INLINE_{N+1} .end to wrap each contiguous piece. I don't want symbols defined at point X in the code to be visible to subs introduced at points prior to X. I think the