LOGO-L> OOPs and Logo

[KERRB@Magill.UniSA.edu.au]

 I've been doing just a little bit of study of object oriented programming 
approach. Here is one of my half baked but serious comments that ir responded 
to will help me get my head around the issues more comprehensively.

 Serious programming seems to have evolved into OOPs, I gather because its a   
reliable way to write BIG programs using teams efficiently.

 The main principles of OOPs from my (limited) reading are ENCAPSULATION 
(protecting procedures from outside interference) and INHERITANCE (take one of 
thousands of library objects and tweak it to meet your ends).

 My question / comment is this:-
 How does the study of logo by students at Primary / Secondary level prepare 
them for these apparently important OOPs principles (encapsulation and 
inheritance) if they decide to go on to a serious study of computer science?

 Is it possible to write a logo procedure that displays either encapsulation or 
inheritance? If so, could someone post one?

 Are these questions relevant to the future evolution of Logo, how we visualise 
it being used for young people?

 -- Bill Kerr

ps. I'm aware that there is a fully fledged Object Logo but that is only 
available on the Mac., which is my excuse for not having seen it.
---------------------------------------------------------------
Please post messages to the Logo forum to logo-l@gsn.org.  Mail
questions about the list administration to logofdn@gsn.org.  To
unsubscribe send    unsubscribe logo-l    to majordomo@gsn.org.