Chaim Frenkel writes:
What about formating the output as a value that can be used by eval?
%hash = (a = 1, b = 'the world');
print "%{hash}\n";
('a' = 1, 'b'= 'the world')
Interesting.
And as for having to escape % in printf strings. Why not enable the
interpolation if the
Michael G Schwern writes:
RFC 142 may help out existing un/pack users, but does nothing to help
in the understanding of un/pack by native speakers of Perl.
I'm starting to think this is largely a documentation issue.
Yes. Please put this thread out of our collective misery.
Nat
Michael G Schwern writes:
Creset %hash should reset the hash iterator, instead of calling
Ckeys or Cvalues as is currently the case.
Sounds good, except the name. reset() already does something.
Currently, reset() is for clearing large swaths of global variables (a
dubious feature) and
Michael G Schwern writes:
Okay, the example says on thing and the text of the proposal says
another.
Sorry, I thought you were talking about a different section of code.
I'll resubmit tomorrow.
So you're proposing that Csort %hash act like Cmap { $_ =
$hash{$_} } sort keys %hash? I can
Karl Glazebrook writes:
Yes. And for the record I also think the current approach of lets generate
ten million RFCs and Uncle Larry knows best is nuts. There are already
too many RFCs on this topic alone to grasp coherently.
Do you have a better suggestion?
Nat
Dan Sugalski writes:
Sure, it's handwaving, but it's handwaving with a purpose. What I don't
want is for people to get bogged down by the limits of what perl 5
provides, or what looks to be some sort of reasonable extrapolation
of those features.
If a fully working tie's what you need,
Tom Christiansen writes:
Also, there are many array operations (push, pop, etc) still not
supported by tie.
Eh? Either that's no longer true, or we're doing the time warp again.
Right you are. I'm still living in the 20th century :-)
Nat
