Time to invent a different file format to hold meta data info

[Unknown W. Brackets]

Well, an API allows programatic reduction, handshaking (version 
upgrades), and the like.  A file format can do some of these things as 
well, but it starts to get more complicated, and you start wasting space 
for bc, etc. etc.

Also, a file format would have to be generated by running the compiler, 
e.g. compiling the file; the original post was about using this for an 
IDE.  How is it useful to have to compile it first before proper 
information is available?

Sure, the compiler could be run by the IDE, and the result returned as a 
file... but you can call that "meta data file", I'll still call it "an 
API that uses a temporary file."

-[Unknown]


Kagamin wrote:
> Unknown W. Brackets Wrote:
> 
>> Well, I'm not so sure.  Every time you invent meta data, someone will 
>> invent a language that goes outside that meta data.  It's reality.
> 
> API will do the same.
> 
>> Programs would benefit from such an API as well; it could provide basic 
>> runtime information (mangling, dynamic compilation, etc.)
> 
> We can have this API for metadata. And what if I want full type information?