Compiler project
OvermindDL1 <[email protected]> Sat, 16 Jan 2010 19:58:54 -0700
| Newsgroups | gmane.comp.parsers.spirit.devel |
|---|---|
| Message-ID | <[email protected]> |
Has a compiler project been decided on? Also, I think we should do what most compilers do, every element in the generated tree should not only have the information of what it is, but also the iterator range in the source location of the data that created it, and things higher in the tree contain the ranges of the things that are lower and so forth, this would vastly simplify error reporting, and error reporting is *always* a huge boon to compiled and scripting languages alike. It is of course not necessary if we somehow end up generating the final LLVM bitcode directly from the representation, but if we do not, then good error reporting should be an absolute. I think we could build the LLVM representation directly with a bit of work, just wonder which method is better... Some languages, depending on what is chosen, will require post-tree visitation before LLVM generation, so that would require things for sure. ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev