[nem-en] Multiple project solutions

[Kamil Skalski]

Michal just reminded me, that for this to work we would really need to
share all types loaded from any external assemblies, which is
definitely more work to do (as I pointed in my first mail on the
topic). Otherwise any type comparisons during compilation would fail:
for example if you check if you can call method   f : int -> void
(imported from external project) using argument of type int from
current compilation, you must check if int == int, but since they come
from different LibraryLoaders the comparison fail...

The solution would be to share library references and use centralized
storage for created external types...

2007/1/8, vc <vc at rsdn.ru>:
> > 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.
>
> Kamil, you can do this?
> Also to us is necessary API which provide support for copy TypeBuilder (and
> so on) in others NamespaceTree and to delete them if they have become
> outdated.
>
>
>
>
> _______________________________________________
> https://nemerle.org/mailman/listinfo/devel-en
>


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