[nem-en] Multiple project solutions

[Kamil Skalski]

>
> But, you do don't consider a one problem.
> If Nemerle becomes mainstream language right away it will be used by lamers,
> novice and inattentive coders. And (by Murphy's law) if anything can go
> wrong, it will... and at the most inopportune time.

Our assumption from the beginning was that macros will be used by
advanced programmers. I guess the special API and markers are a way to
go instead of limiting features at all.

>
> Besides we compile method body scores of times. It makes duplicate
> types/members and cause error messages.

Is it because of some macro adding code? Probably all macros (maybe
even those running from attributes) adding new stuff should check if
they are not duplicating anything. The problem can be observed when
compiling methods with such expression level macros, which contain
some error - compiler tries to compile again in error mode and this
yield duplicate members.
Currently the adviced solution is to check if compiler is in ErrorMode
before generating new classes/ members.


>
> I see one way in this situation. We must allow add (from expression macro)
> top level code only by way of special methods (API). In Integration this
> methods do nothing. Also code added by this method must be mark with some
> flag. It flag mast hide generated code from direct user asses.
>

Define*  are such methods. They could check if we are already in
method bodies compilationg stage AND in intellisense mode.


-- 
Kamil Skalski
http://nazgul.omega.pl