[nem-en] Multiple project solutions

[Kamil Skalski]

They would need to share a couple of objects - especially
InternalTypeCache and LibraryReferenceManager. This seems possible to
do, but the largest problem is with projects having different set of
references. We need a functional-style data-structure, which could
describe different sets of references to be used by projects'
ManagerClasses - and then we need to manage them in a quite complex
way: every change of references needs to trigger computing disjoint
sets of references, create their tree defined by inclusion relation
and assign proper nodes to every project / ManagerClass.

As I can see LibraryReferenceManager contains references directly to
NamespaceTree nodes... I need to think if this is a problem, but I
suspect something bad here.



2007/1/6, Igor Tkachev <it at rsdn.ru>:
> Hello devel-en,
>
> Michal, Kamil,
>
> We have another issue related to the multiple project solutions and we
> need your help.
>
> We can have more than one project in the same solution and each
> project has associated ManagerClass. Currently, ManagerClass can load
> types from assemblies. We need ManagerClass to be able to use types
> from other projects, I guess it should read types from other
> ManagerClasses.
>
> Can we do it?
>
> --
> Best regards,
> Igor
> mailto:it at rsdn.ru
>
>
>
> _______________________________________________
> https://nemerle.org/mailman/listinfo/devel-en
>


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