I stumbled on this why playing around with the TypedClass class.
I think I can convince myself that it's a natural outgrowth
of Unicon's philosophy that inheritance is considered as
taking methods and fields from the parent class instead of
extending the parent class - but that isn't going to stop me
from grumbling (softly).
Consider the following program:
-------------------------------------------------------
class A()
initially
write("In A, self is ",type(self))
end
class B: A()
initially
self.A.initially()
write("In B, self is ",type(self))
end
procedure main()
A()
write()
B()
end
---------------------------------------------------
First, a question: What do you think the output of the
program should be?
Now run the program - is the output what you expected?
grumble...talk about parents living vicariously through
their children...
--
Steve Wampler <[EMAIL PROTECTED]>
National Solar Observatory
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unicon-group
