> >> Means: When starts Pharo refactoring its own code or AST parser itself? >> > PetitParser provides exactly that: A parser has a meta-model to be changed at > runtime. > > With Opal, we use an AST for everything that has transformation support of > the RB. > > >> Maybe a too unclear question, but i hope someone can understand what i mean >> ... :-) >> > You are always
Hi Marcus! PetitParser ... Yes. A paradigm chance already. I was thinking of a data flow analysis parser, that "profiles" through a running system, looking out for relevant and irrelevant "data control & logic structures" (like reducing Pharo source from "unused" code), backtracking the growing of finally thrown or unused data, thus reducing the system to the minimum of relevant code by itself. Means - I see a new paradigm change coming up. Is's like sticking "PetitParser" in its own ass, letting PetitParser analyze its own dataflow, automatically replacing PetitParser by its evolutionary child. What source structures could be generated, that are still readable and changeable by humans?? Guido
