On Mon, 18 Sep 2000 13:26:45 -0700, Glenn Linderman wrote:
Read RFC 241 for a brief overview of pseudo-hash problems.
I've already read RFC 241. Re-reading in this context results in the following
comments/quests for information. The remaining quotes here come from RFC 241...
On Thu, 14 Sep 2000 18:37:22 -0500, David L. Nicol wrote:
print "Today's weather will be ${weather-temp} degrees and sunny.";
which would follow the "You want something funny in your interpolated
scalar's name or reference, you put it in curlies" rule.
I too feel that an approach like
On Fri, 15 Sep 2000 01:36:50 -0800, Michael Fowler wrote:
Or maybe an alternative, using :
"foo foo(arg, arg, arg) bar"
"foo { foo(arg, arg, arg) } bar"
Ah, yes, {...}, I kinda like that. Unfortunately, in regexes, /{1,3}/
means matching 1 to three ampersands. There's a slight
On Tue, 05 Sep 2000 19:08:18 -0600, Tom Christiansen wrote:
exists (sometimes causes autovivification, which affects Ckeys)
That's not technically accurate--exists never causes autovivification.
print exists $hash{foo}{bar}{baz};
use Data::Dumper;
print Dumper
On 1 Sep 2000 20:59:10 -, Perl6 RFC Librarian wrote:
When omitted, the second argument to Cbless currently defaults to the
name of the package from which the call is made.
The word "from" doesn't look like it's been used 100% correctly.
"Being called from" suggests that it's the name af
On 1 Sep 2000 20:59:10 -, Perl6 RFC Librarian wrote:
This RFC proposes that the second argument to Cbless be made
mandatory, and that its semantics be enhanced slightly to cover a
common, ugly, and frequently buggy usage.
Ooh, how about this alternative.
There must be an RFC making the
On Sun, 27 Aug 2000 06:14:00 -0700, Matt Youell wrote:
So an int gets stored as two bytes and not
four or eight.
Gee, I thought it was more like 30. The savings in bytes don't look too
impressive in this case. 4 byte addition is as fast as 2 byte addition
on most pmodern platforms -- and you
On Thu, 24 Aug 2000 13:27:01 -0700, Nathan Wiger wrote:
It's a pain if you want to support both function-oriented and
object-oriented calling forms, as CGI.pm does. For example, you can use
both of these:
print header;
print $r-header;
with CGI.pm. Now you need a self_of_default special
