Code Comments
Programming Forum and web based access to our favorite programming groups.In article <lb33c.1733$w3.8225@zonnet-reader-1>, lohen@versateladslREMOVE.be says... > Hello Andreas, > > "Andreas Moroder" <amoroder@sb-brixen[nospam].it> > schreef in bericht news:c2hvqv$1sf$1@news.flashnet.it... > > > Use the MESSAGE ... METHOD construct for both init methods > declaring an alternate METHOD name and corresponding definition. > > Someting like: > > CREATE CLASS a > EXPORT: > MESSAGE init METHOD a_init > END CLASS > > CREATE CLASS b > EXPORT: > MESSAGE init METHOD b_init > END CLASS > > .... > > METHOD a_init ( ... ) > ... > > METHOD b_init ( ... ) > ... > > Same goes for any other message that needs to figure in both classes ingenious, but the private data are still exposed to each other in a common file-wide pool. I suppose that if you were careful about chosing the var names, you could avoid collisions...
Post Follow-up to this messagePowered by vBulletin
Copyright 2000-2006 Jelsoft Enterprises Limited.