Darren Duncan wrote:
Larry had some ideas for dealing with the problem, but this is a
matter that should be more widely discussed, particularly among
implementers and such.
A general thought is that a parameter could be marked so that any
argument passed through it is effectively snapshot (
As a follow-up to this thread, I discussed the matter on #perl6 with
Larry today (before the thread on mutable arguments), and I learned
that one of my main concerns, of inconsistency between different
collection types, is not valid.
http://colabti.de/irclogger/irclogger_log/perl6?date=2007-05
All,
Something that tops my current list of Perl 6 features to desire, or
design flaws to deal with, concerns protecting private attributes of
our objects from being mutated outside of our control due to their
being assigned to from arguments to our routines that are mutable.
I want to raise
Author: audreyt
Date: Thu May 17 00:29:36 2007
New Revision: 14392
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S04.pod
doc/trunk/design/syn/S06.pod
Log:
* Fix thrice misspelling of &?BLOCK as $?BLOCK.
Modified: doc/trunk/design/syn/S02.pod
===
