what theo d hondt told us a while ago is that pascal or oberon they did not store bytecode but compressed ast and it was shorter than bytecode
Stef On Apr 27, 2010, at 1:44 PM, Lukas Renggli wrote: >> So what I want to explore is to have a very compact representations of ASTs, >> but one >> that does not lose information *and* that allows the AST to be annotated >> with non-textual >> objects even when it's compressed. > > Indeed, annotations (or properties) get lost when serializing an AST > as source code. However I doubt that a different encoding of the AST > as a string is any more efficient than just storing the (compressed) > original source code (see the tests of AstSerializer). Also having a > "custom pretty printer" and a "custom parser" makes it kind of > difficult to have code that cannot be represented with the standard > AST, as this is for example the case in Helvetia. > > What about storing the annotations (or properties) separate the the > source string and map them back to the AST after parsing? > > Lukas > > > > > > >> >> Marcus >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
