From: [EMAIL PROTECTED]
Date: Wed, 26 Jul 2006 14:44:41 -0700 (PDT)
Author: allison
Date: Wed Jul 26 14:44:40 2006
New Revision: 13593
. . .
Modified: trunk/docs/pdds/clip/pdd15_objects.pod
==============================================================================
--- trunk/docs/pdds/clip/pdd15_objects.pod (original)
+++ trunk/docs/pdds/clip/pdd15_objects.pod Wed Jul 26 14:44:40 2006
@@ -212,6 +212,13 @@
-- the offsets of a class' attributes will change from child class to child
class)
+{{ NOTE: one feature I'd like to have is some way to access a list of
+the object's attributes. The particular use I have in mind is dumping
+the attributes of an object a la Data::Dumper. It abuses the notion
+of 'opaque object', so I could be persuaded it's not a good idea. On the
+other hand, it could be an introspective capability offered by Parrot
+but not directly exposed in the HLLs. }}
+
ParrotClass PMCs also have the "I am a class" flag set on them.
IMHO, introspection capability is *always* a good idea. Opaque objects
are nice, but the usefulness of opacity is situational; you wouldn't
want your objects to be opaque to debugging tools, for example.
-- Bob Rogers
http://rgrjr.dyndns.org/
