If memory serves me right, James Michael DuPont wrote: > I just want to know how where we can put it. The Microsoft IL > has a whole section on meta-data,
AFAIK, that just holds the offset, line number and filename. IIRC the JVM had a LineNumberTable and VarNameTable for debugging which were declared as ``attributes'' to each method in the .class tree. I suppose VarNameTable is totally irrelevant for Parrot ... > yes I agree, I just want to be able to reconstruct the tree for > debugging or reverse engineering (if the compiler that produced the > bytecode whats to produce this). Optimisations ? ... (bang, there goes the line numbers ;) > Normally you dont need this information, I just want to know how I can > store it if I *do* need it. > > The metadata from the c++ that i am extracting even exceeds the size of > the sourcecode itself. > > yeah, that is the idea. Reflection and introspector require the > meta-data, that can be read by special reflection operations. I think Parrot is going to *need* reflection operations :) ... You might be able to extract information like you do with C# , with reflection looping over the methods. Btw, your RDF stuff wouldn't be what I call "metadata" :) .. it's data itself in a pre-processed format. > > IMCC can pick out > > the chunks of IMC, generate bytecode, .line 42 "life.fubar" ? Gopal PS: don't look at me like that , I don't know anything about debugging eval()... -- The difference between insanity and genius is measured by success