[nem-en] Multiple project solutions

[Kamil Skalski]

07-01-07, NoiseEHC <NoiseEHC at freemail.hu> napisał(a):
> I am not sure how you show the macro expansion but if you have to run it
> then all you
> can do is:
> - if there is a compiled macro dll then it is ok
> - if there is none then just parse the name and maybe the "syntax",
> otherwise
> if there is no colorization then it is acceptable (if you colorize by
> using "syntax")

True, this should be possible with in-memory macro definitions
obtained from project... though it requires some work. Currently we do
not hold the metadata of macros during their compilation - we just
generate the classes, which contain the encoding of their
specification.
After we create such metadata of macros being compiled, add it into
some collection, it could be used to inject into another project. Such
macros could be shown as "uncompiled" in hints.

>
> What I wanted to say that you should not try "executing" uncompiled macros.
> (It is just craptalk from me, probably you did realized that already :)
>
> Igor Tkachev wrote:
> > Hello NoiseEHC,
> >
> >
> >>> One more concern. What about macros? They also should be available
> >>> and workable.
> >>>
> >>>
> >>>
> >> I would strongly suggest to use macros only from the last compiled
> >> version. You really should
> >> not waste time trying to use halfway implemented macros from source. It
> >> will not succeed...
> >>
> >
> > I quite realize that.
> >
> >
> >> And users will simply accept that if they really want to see macro
> >> expansion/coloring then recompile after each modification...
> >>
> >
> > I don't think so they will accept it simply. For example, showing
> > lots of errors because of not compiled macro is not acceptable. So, we
> > will have to deal with macros anyway.
> >
> >
>
> _______________________________________________
> https://nemerle.org/mailman/listinfo/devel-en
>


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