Przemysław Czerpak wrote:
>
> I guess you are talking about :start() method not execute.
> It works because in Clipper and [x]Harbour there is no difference
> between messages send to access instance variables and to execute
> method.
> We have ::atStart variable so
> ::atStart()
> execute default access function which push this variable on the stack.
>
> BTW please also note that in xbase++ variables are also not accessed
> directly but using messages which executes some methods and you can
> define your own ACCESS and ASSIGN methods. It was the reason why I asked
> about threadID conversion. The fact that sth is documented as instance
> variable does not have to mean that it's real instance var. It can be
> sth completely different encapsulated in ACCESS/ASSIGN methods.
>
You are right Przemek.
In Xbase++ this concept is achieved with get/set methods which
I am employing in hbXBP effectively.
VAR s_title PROTECTED
METHOD title SETGET
METHOD XbpWindow:title( cTitle )
IF hb_isChar( cTitle )
s_title := cTitle
ENDIF
RETURN s_title
and rest everythis is done with s_title.
This was the most struggled feature to emulate Xbase++ class behavior.
-----
enjoy hbIDEing...
Pritpal Bedi
_a_student_of_software_analysis_&_design_
--
View this message in context:
http://n2.nabble.com/SF-net-SVN-harbour-project-13991-trunk-harbour-tp4632457p4633241.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
