Hello
Przemysław Czerpak wrote:
>
> It's not such trivial. It's necessary to modify compiler, generated
> PCODE and HVM. It will be also good to ask group if such syntax
> extension is acceptable:
> thread static s_var init { || hb_datetime() }
> or maybe we should add to sth.ch:
>
> #command thread static <!var!> init <initcode> => ;
> thread static <var> initblock <{initcode}>
>
> and then to compiler support for:
>
> thread static <var> initblock <block>
>
> so programmer can simply make:
>
> thread static s_var init hb_datetime()
>
This issue essentially resolvs around _performance_.
So if the PP method described as above places no overhead
then that's it! But if it checked everytime the variable is
accessed then there are other ways also to simulate it.
>> ? __clsParent( oBcd:classH, "MYCLS" ) // what will be the result ?
>
> .T.
>
> METHOD isDerivedFrom( cClassName )
> RETURN __clsParent( Self:classH, cClassName )
>
>
I am delighted to hear this.
Will implement in hbXBP code shortly.
> There is much more "default" methods in different OOP implementations
> in xbase world. I do not think that it's good idea to adding separately
> some of them because some of us wants to use it in some project without
> bigger vission about final code.
> I do not know which system methods use xbase++ and which of them are part
> of object and which ones belongs to class object only.
>
I understand this concern.
Because I have a solution as above, I do not need it by default anymore.
Thanks for clarifications.
Regards
Pritpal Bedi
--
View this message in context:
http://old.nabble.com/INIT-EXIT-Procedures---Thread-Wise-tp27302415p27320680.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
