[nem-en] ManagerClass.Instance == pain!

Kamil Skalski kamil.skalski at gmail.com
Sat Nov 18 22:39:40 CET 2006


I have done some more refactoring, but I think it is not entirely
possible to eliminate ManagerClass.Instance without more performance
loss and breaking much of API and making its using harder. Moreover,
it would in general require all code quotations to be used only where
special "compiler context" is available, so requiring macro writers to
pass this context to every utility function they use.

Considering it, why ManagerClass.Instance is so bad for you? Maybe it
would be enough to mark this field with the special attribute, so
every thread can have its own instance (as we talked some time ago on
the forum).

On 11/17/06, vc <vc at rsdn.ru> wrote:
> Hi,
>
> We have a lot of ManagerClass.Instance related problems.
>
> Kamil, could you, please, finish moving to the instance based compiler
> engine.
>
> Vlad
>
>
> _______________________________________________
> https://nemerle.org/mailman/listinfo/devel-en
>


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



More information about the devel-en mailing list