Subject: RE: Re[2]: ManagerClass.Instance == pain! - msg#00096

Previous Message by Date: click to view message preview

RE: ManagerClass.Instance == pain!

> On the other hand we could introduce some more utility macros to > simplify the transition. Yes! :) In true macros is fine. > Like module from my example would become > instance class marked with ManagerAccess macro and having Manager > passes in its newly introduced constructor... Anyways I expect it > could still be very irritating for users to face such big design / API > change. You should think about future users. Language is not released yet.

Next Message by Date: click to view message preview

Re: What is additional_decls?

On 11/18/06, vc <vc@xxxxxxx> wrote: > It would be really good to make Message.Debug and Trace.WriteLine work > together - maybe just check in Message.Debug if we are in completion > mode and use Trace or some more elegant way of binding two output > streams... May be use Trace in Meaasge instead Console? Trace support Listeners which can be used to add listeners. Just a little remark ;) Trace and Trace.Listeners are static - you will end up with all the messages from all Managers put into all the windows of all listeners... -- Kamil Skalski http://nazgul.omega.pl

Previous Message by Thread: click to view message preview

Re[2]: ManagerClass.Instance == pain!

Hello Kamil, Can we get a macro which will add 'Instance = this;' at the beginning of every single public method/property of ManagerClass and its children? I believe in this case this problem could be solved without any user impact. Saturday, November 18, 2006, 7:06:56 PM, you wrote: >> >> and pass it everywhere... >> >> It would break literally ALL existing code. >> > On the other hand we could introduce some more utility macros to > simplify the transition. Like module from my example would become > instance class marked with ManagerAccess macro and having Manager > passes in its newly introduced constructor... Anyways I expect it > could still be very irritating for users to face such big design / API > change. -- Best regards, Igor mailto:it@xxxxxxx

Next Message by Thread: click to view message preview

RE: ManagerClass.Instance == pain!

> On the other hand we could introduce some more utility macros to > simplify the transition. Yes! :) In true macros is fine. > Like module from my example would become > instance class marked with ManagerAccess macro and having Manager > passes in its newly introduced constructor... Anyways I expect it > could still be very irritating for users to face such big design / API > change. You should think about future users. Language is not released yet.