[svn:parrot] r38063 - in trunk: docs/pdds/draft include/parrot

[whiteknight at svn.parrot.org]

Author: whiteknight
Date: Sat Apr 11 13:22:29 2009
New Revision: 38063
URL: https://trac.parrot.org/parrot/changeset/38063

Log:
remove some mentions of PMC_*_val from a few documentation sources, so people don't think that they still exist

Modified:
   trunk/docs/pdds/draft/pdd08_keys.pod
   trunk/docs/pdds/draft/pdd16_native_call.pod
   trunk/include/parrot/oo.h

Modified: trunk/docs/pdds/draft/pdd08_keys.pod
==============================================================================
--- trunk/docs/pdds/draft/pdd08_keys.pod	Sat Apr 11 12:47:18 2009	(r38062)
+++ trunk/docs/pdds/draft/pdd08_keys.pod	Sat Apr 11 13:22:29 2009	(r38063)
@@ -47,8 +47,8 @@
 For this reason the following structure was produced.  Individual keys (e.g. a
 single C<Integer> or C<String>) are stored in a C<Key> PMC.  The type of the
 key is encoded in the private flags of the PMC as specified below.   The value
-of the C<Key> PMC is stored in the PMC's cache (i.e. C<PMC_pmc_val(key)>,
-C<PMC_int_val(key)>).
+of the C<Key> PMC is stored in the PMC's data structure internally and can be
+accessed using the appropriate get_* VTABLE functions.
 
 For example, indexing the multidimensional array C<@foo[$a,12;"hi"]>
 produces three PMCs; one with a PMC type, one with an integer type
@@ -79,8 +79,8 @@
 
 
 The C<KEY_register_FLAG> is used to indicate that value if the key is in a
-register.  In this case, C<PMC_int_val(key)> contains the number of a register
-of the appropriate type that contains the value.
+register.  In this case, the Key PMC's data contains the integer number of the
+appropriate register in the current context.
 
 Parrot must also have a way to combine multiple keys into a key that can be
 treated as a single unit.  This is done by forming a singly linked list such

Modified: trunk/docs/pdds/draft/pdd16_native_call.pod
==============================================================================
--- trunk/docs/pdds/draft/pdd16_native_call.pod	Sat Apr 11 12:47:18 2009	(r38062)
+++ trunk/docs/pdds/draft/pdd16_native_call.pod	Sat Apr 11 13:22:29 2009	(r38063)
@@ -99,18 +99,15 @@
 
 =item 2
 
-A pointer to a short, taken from an P register of an int-like PMC. On return
-from NCI, the PMC_int_val will hold the new value.
+A pointer to a short, taken from an P register of an int-like PMC.
 
 =item 3
 
-A pointer to an int, taken from an P register of an int-like PMC. On return
-from NCI, the PMC_int_val will hold the new value.
+A pointer to an int, taken from an P register of an int-like PMC.
 
 =item 4
 
-A pointer to a long, taken from an P register of an int-like PMC. On return
-from NCI, the PMC_int_val will hold the new value.
+A pointer to a long, taken from an P register of an int-like PMC.
 
 =item t
 

Modified: trunk/include/parrot/oo.h
==============================================================================
--- trunk/include/parrot/oo.h	Sat Apr 11 12:47:18 2009	(r38062)
+++ trunk/include/parrot/oo.h	Sat Apr 11 13:22:29 2009	(r38063)
@@ -25,10 +25,7 @@
 } PARROT_CLASS_DATA_ENUM;
 
 
-/* Objects, classes and PMCarrays all use the same data scheme:
- * PMC_data() holds a malloced array, PMC_int_val() is the size of it
- * this simplifies the GC mark phase a lot
- *
+/*
  * The active destroy flag is necessary to free the malloced array.
  */
 #define SLOTTYPE PMC*