At 7:54 AM -0400 8/22/02, 'John Porter' wrote: >Dan Sugalski wrote: >> The intent ultimately >> is that you hand an AST, and potentially some rules, to IMCC and it >> creates bytecode for you from it. > >That's different, then. Then the whole issue of syntax goes away. >Unless the data interchange format is textual; but even then, you'd >want a syntax highly tuned for tree structures (and other things), >and the current syntax doesn't sound like it fits this criterion. Right, the current syntax is definitely not tuned for many things. That's OK, it was a first cut, and the core is solid enough to build on. The next step is to get an AST format defined and get IMCC to eat it. Then we rip out the text interface it has now, and make it a layer on top of the AST parser. Got some free time, John? -- Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai dan@sidhe.org have teddy bears and even teddy bears get drunk