Peter Scott wrote:
$employee{$empno}{SAlARY} -= 10_000; # IPO failure
$employee{$empno}{FAX} = '888-555-1212';
First one got the wrong key when my finger slipped on the shift key, second
one got it when I misremembered FAX instead of FACSIMILE. But in neither
case
At 03:37 PM 9/17/00 -0700, I wrote:
Brainstorming How about an attribute for hashes:
my %foo : fixed;
And now new keys cannot be inserted into the hash just by assigning to
their values. As to how you could put them there... well the ideas that
come to mind are [snipped]
At 10:56 AM 9/16/00 -0400, Michael G Schwern wrote:
Pseudo-hashes are not a good/clean way to implement typed objects.
Why? Can't do multiple inheritence (without *alot* of contortions).
And there's also the inefficiencies of untyped pseudo-hash access.
Pseudo-hashes made some sense in the
On Sun, Sep 17, 2000 at 03:37:07PM -0700, Peter Scott wrote:
However, while we've got ways in P6 to do objects better without
pseudo-hashes, a major benefit of them to me is nothing to do with objects,
and that's the ability to fix the keys of a hash. I would like to see this
retained.
=head1 ABSTRACT
Pseudo-hashes and the associated fields pragma shoule be removed from
Perl 6.
A few counter points:
Removal of pseudo-hashes should not stop us from using this (or a
similar mechanism) under the covers in perl6 to implement strongly typed
objects.
AFAIK, most of the pain
On Sat, Sep 16, 2000 at 10:31:55AM +0100, Hildo Biersma wrote:
AFAIK, most of the pain in the implementation is caused because any old
array can be 'promoted' into a pseduo-hash at any-time. If
pseudo-hashes always have to be pre-declared (eg, can only be created
through fields::new()) and
=head1 VERSION
Maintainer: Michael Schwern [EMAIL PROTECTED]
Date: 16 September 2000
Mailing List: perl6-language
Number: ?
Version: 1
Status: Developing (Last Call)
Reply-To: perl6-language @perl.org
This and other RFCs are available on the web at
