cvsuser 03/03/11 14:14:50
Modified: docs/pdds pdd15_objects.pod Log: more of the text Revision Changes Path 1.4 +25 -1 parrot/docs/pdds/pdd15_objects.pod Index: pdd15_objects.pod =================================================================== RCS file: /cvs/public/parrot/docs/pdds/pdd15_objects.pod,v retrieving revision 1.3 retrieving revision 1.4 diff -u -w -r1.3 -r1.4 --- pdd15_objects.pod 11 Mar 2003 21:42:20 -0000 1.3 +++ pdd15_objects.pod 11 Mar 2003 22:14:50 -0000 1.4 @@ -73,6 +73,10 @@ useful with these things rather than just (potentially) throwing an exception. +Any PMC that meets these criteria can be considered an object. Objects +do I<not> have to have corresponding classes, though it's a fairly +common occurrence. + =over 4 =item Get and set properties @@ -80,6 +84,10 @@ Strictly speaking, getting and setting properties is a PMC thing rather than an object thing, as PMCs are +=item Get a property hash + +=item Get and set attributes + =item =back @@ -148,9 +156,25 @@ inherit from a class because the class is from a different object universe. +As an example, assume you have a class A, which inherits from class +B. The classes are incompatible, so Parrot can't automatically meld B +into A, as it might if they were. When instantiating an object of +class A, Parrot will automatically instantiate an object of class B +and embed it in the object of class A. The object of class B is class +A's delegate--when a method call comes in that A can't handle, that +method call is delegated to B. + =item Parent class +Also called the super-class. The parent class is, in an inheritance +situation, the class being derived from. If A derives from B, B is the +parent class of A. + =item Child class + +Also called the sub-class. The child class is, in an inheritance +situation, the class doing the deriving. If A derives from B, A is the +child class. =back
