Re: IMCC, classes metadata

2003-10-24 Thread Leopold Toetsch
Melvin Smith [EMAIL PROTECTED] wrote: Basically all metadata has to be collected before any code can be emitted. I was thinking of generating an _init routine that creates the classes, so we have several possibilities. Why? A class definition should AFAIK end up in the constant table as a

Re: IMCC, classes metadata

2003-10-24 Thread Dan Sugalski
On Thu, 23 Oct 2003, Melvin Smith wrote: I'm working on getting class syntax added to PIR. It appears IMCC's way of emitting instructions as it collects compilation was a mistake (mine) and isn't going to work for metadata that needs to be initialized first. Basically all metadata has to

Re: IMCC, classes metadata

2003-10-24 Thread Melvin Smith
At 08:36 AM 10/24/2003 +0200, Leopold Toetsch wrote: Melvin Smith [EMAIL PROTECTED] wrote: Basically all metadata has to be collected before any code can be emitted. I was thinking of generating an _init routine that creates the classes, so we have several possibilities. Why? A class

Re: IMCC, classes metadata

2003-10-24 Thread Leopold Toetsch
Melvin Smith [EMAIL PROTECTED] wrote: At 08:36 AM 10/24/2003 +0200, Leopold Toetsch wrote: Why? A class definition should AFAIK end up in the constant table as a class PMC specifying the inheritance and attributes. So a .class directive is from parsing POV a constant definition, like a string

IMCC, classes metadata

2003-10-23 Thread Melvin Smith
I'm working on getting class syntax added to PIR. It appears IMCC's way of emitting instructions as it collects compilation was a mistake (mine) and isn't going to work for metadata that needs to be initialized first. Basically all metadata has to be collected before any code can be emitted. I