At 4:05 PM -0400 6/8/05, Tolkin, Steve wrote:
Summary: An ordered hash that does not support deletes could cause a
user visible bug. At a minimum it should support the special case
of delete that is supported by the Perl each() operator.
Details: This Week in Perl 6, May 25, 2005-May 31,
From: Dan Sugalski [EMAIL PROTECTED]
Date: Wed, 8 Jun 2005 16:22:35 -0400
At 4:05 PM -0400 6/8/05, Tolkin, Steve wrote:
. . . Dan Sugalski says: I'd just pitch an exception if code
deletes an entry ...
Perhaps this is OK, because this code is intended for internal use
Summary: An ordered hash that does not support deletes could cause a
user visible bug. At a minimum it should support the special case of
delete that is supported by the Perl each() operator.
Details: This Week in Perl 6, May 25, 2005-May 31, 2005
Tolkin, Steve wrote:
Summary: An ordered hash that does not support deletes could cause a
user visible bug. At a minimum it should support the special case of
delete that is supported by the Perl each() operator.
The proposed ordered hash ist mostly used for Parrot internals. If a
user
