At 7:29 PM -0700 1/7/03, John Williams wrote:
All variables in parrot are implemented as PMCs, and all PMCs may be accessed with a string, integer, or PMC subscript or set of subscripts. For PMCs that don't do subscripting this will be a fatal error, for those that do it'll do whatever the PMC is supposed to do. (In the case of $0, do the lookup)On Tue, 7 Jan 2003, Dan Sugalski wrote:>2. There is a primitive "array" type that is promoted to an >objectified Array class when needed. This would be analogous >to the int/Int distinction for primitive numbers. This would be >visible to programmers, but may be acceptable for the same >reason as the int/Int types are.Not unless Larry really insists. "Primitive" arrays aren't sub-, super-, or side-classes of objects--they aren't objects at all. (They're arrays, hence the name "array") You may be able to treat them in some ways as objects, but that doesn't make them objects any more than treating arrays like integers makes them integers.Perhaps you could explain how the $0 object will work in your mind. A5 assert that $0 is a object, and it behaves as an array and a hash, depending on how you subscript it. Typeglobs are gone, and we're all hoping the TIE interface is gone too, so how will this effect be accomplished?
If you really, really, really wanted to, you could consider PMCs as objects. You may have to squint really hard and paint them pink, but...that PMCs do is allow you to call a method on them, which we don't guarantee will work as we don't guarantee there's even a package associated with a PMC)
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
