On Mon, 30 Mar 2009 02:09:28 -0400, Unknown W. Brackets
wrote:
Check out clang. LLVM frontend for C, C++, and Objective-C which has
similar IDE intergration in mind.
Maybe ldc can take this route?
Actually, I think it would be much more fruitful to have a standard way
to integrate a comp
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 compil
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 (manglin
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.
Programs would benefit from such an API as well; it could provide basic
runtime information (mangling, dynamic compilation, etc.)
That said, as far as refle
Unknown W. Brackets Wrote:
> a standard way to integrate a compiler into an IDE
You meant *compilers*? D1, D2, D3 etc.
Not only IDE will benefit from extensive metadata. Compiler and runtime
reflection will too.
Does that mean I should be holding my breath for a -DIDE switch to
launch an IDE that gets the syntax highlighting right? Heh.
Seriously, I do agree that was a smart choice. I wish its output were a
bit more semantic, but things like that can be fixed. Having correct
parsing is priceless, a
Unknown W. Brackets wrote:
Of course, I'm sure a better API could be devised. This sort of format,
if properly standardized, could be used to make IDEs much more
efficient. It would also allow for much better and more accurate error
reporting, and the compiler could be loaded as a shared obje
Actually, I think it would be much more fruitful to have a standard way
to integrate a compiler into an IDE. An API would be needed with things
like: (all optional)
1. Lex a file (returning basic token information.)
2. Parse a file (returning some sort of standardized syntax tree.)
3. Compile
I hope it will be integrated to the Compiler. As IDE should not deal with
language changes.
Dealing with parsing sources of D1, D2, D3, D4... is actually cumbersome.
The IDE development gets hindered because the autocompletion must be able
to parse both D1/D2 and future DMD releases. And en
