Ok, I noted all the use cases.
> On 30 Mar 2015, at 16:25, Thierry Goubier <thierry.goub...@gmail.com> wrote:
>
> A use case:
>
> the ability to test and debug the code generation part of SmaCC.
>
> SmaCC, when compiling a parser, generates dozens of classes and hundreds of
> methods, some of those very long, as a sequence of refactorings (and optimise
> them).
>
> Then SmaCC apply them all in one step.
>
> I'd dream of having a virtual environment where I could test-compile and
> check all those methods, via a system browser, before they are compiled.
>
> Thierry
>
> 2015-03-30 9:10 GMT+02:00 Marcus Denker <marcus.den...@inria.fr
> <mailto:marcus.den...@inria.fr>>:
>
> > On 29 Mar 2015, at 10:32, stepharo <steph...@free.fr
> > <mailto:steph...@free.fr>> wrote:
> >
> > Before that I would like that the compiler outputs classes definition in an
> > environment (that can be the default one) but that can be the one
> > I want and specified from the outside of the compiler.
>
> For installing, it is the ClassInstaller that does that (and yes, it has an
> environment).
>
> What the compiler does not have is to look up references e.g. to symbols
> regarding to an environment, but that is because we
> don’t have that concept right now in the system in general. globals/class
> vars are requested from the class (which defines its environment).
>
> So in general, we first need a use case, else it is not clear what to do…
>
>
> Marcus
>
