Austin Hastings [EMAIL PROTECTED] writes:
s/conses/consensus/g ?
I assumed it was a Lisp reference. ;-)
Jon
Luke Palmer [EMAIL PROTECTED] writes:
Juerd writes:
What happens to the flip flop operator? Will .. in scalar context
remain the same? What comes in place of ...? (An adverb?)
Anyway, to answer what I _do_ know, isn't .. exactly the same as ... in
Perl 5? That was my impression, at least
Matthew Walton [EMAIL PROTECTED] writes:
James Mastros wrote:
Larry Wall wrote:
Well, yes, but sometimes the weights change over time, so it doesn't
hurt (much) to reevaluate occasionally. But in this case, I think I
still prefer to attach the exotic characters to the exotic behaviors,
and
Fred Heutte [EMAIL PROTECTED] writes:
A vote against the proposed switches, for an unbearably lazy (ok,
selfish) reason. Having to use the shift key with any non-alphanumeric
keypress always feels like a lot of extra work. This is why I have long
avoided underscores in variable names.
"Greg Boug" [EMAIL PROTECTED] writes:
So open has to parse the string for a URL and magically use
a http protocol? Not sure I like that idea... Granted, from a
programmatical point of view that looks neater... But what
about the case where you have a file called "http:" (a legal
filename
Tom Christiansen wrote:
Perl already *has* a print operator: "print". :-)
I think what I really want is a tee operator.
The problem with what you have there is that it hides the act of
output within an arbitrarily long circumfix operator whose terminating
portion is potentially very far
Perl6 RFC Librarian wrote:
=head2 Cheating Is Still Possible
Not ignoring the return value is of course no guarantee of doing
anything useful with the return value:
$so_what++ unless defined fork();
But detecting whether 'something useful' is done is squarely in
the realm of
Karl Glazebrook wrote:
Jon Ericson wrote:
But @ and % provide important context clues (if not to perl than
certainly for programmers). We could also eliminate the plural case in
English, but this would be endlessly confusing for native speaker
(err... speakers). Why not change @x so
Karl Glazebrook wrote:
Nathan Wiger wrote:
Yeah, and isn't it cool that Perl gives you easy access to using and
understanding such complex data structures:
print @{ $cars-{$model} };
That "junk" makes it easy to see that you're derefencing a hashref that
contains a key which is
Karl Glazebrook wrote:
Jon Ericson wrote:
I've spent almost a day trying to come up with a polite response to this
suggestion. I have started this mail 3 or 4 times but deleted what I
wrote because it was too sarcastic, angry or dismissive. This RFC
Thanks!
strikes to the very
John Porter wrote:
Mike Pastore wrote:
Highlander variables acknowledge the fact that all variable types (scalar,
array, hash) are simply objects. Objects of different classes, sure; but
still just objects.
Not in Perl.
You get no visual help in cases like
$dog-bark();
Perl6 RFC Librarian wrote:
[snip reconstructionist history and newer-is-better fallacy]
I argue in this Brave New World the distinction between C$x, C@x and
C%x are no longer useful and should be abolished. We might want
to use all kinds of array objects, why should @x be special? Rather
Damian Conway wrote:
When a pair reference is assigned (in)to an array, it remains a
single scalar (referential) value. So:
@array = ( a=1, b=2, 'c', 3 );
assigns four elements (not six) to @array.
The proposed Ckey and Cvalue built-ins (or the
Chaim Frenkel wrote:
What does
$foo = "filename";# 1
$bar = "another";
$gaz = "filename; # 2
^ add " here
Does #2 get the second line or the first?
$gaz contains the second line. Otherwise this:
while ('filename'){print;};
[Reply-To set to [EMAIL PROTECTED]]
Ed Mills wrote:
I actually saw this in the newsgroups and thought it was a neat idea. What
about
println $textvar;
instead of
print "$textvar\n";
Ever so much easier to read and write, prints the arg and appends \n.
You can currently get
[Reply to perl6-language-io as this is an I/O
related.]
Michael Mathews wrote:
Here's a thought. Wouldn't this be cool (see below)?
The idea is that in
Perl 6 you should be able to read from a file handle
one character or one
line at a time (just like you can in Perl 5) BUT if
you just go
[Reply-To set to [EMAIL PROTECTED]]
Ed Mills wrote:
I actually saw this in the newsgroups and thought it was a neat idea. What
about
println $textvar;
instead of
print "$textvar\n";
Ever so much easier to read and write, prints the arg and appends \n.
You can currently get
Ted Ashton wrote:
Thus it was written in the epistle of Tom Christiansen,
Nope. A filehandle is a singular whatzitz. It thus mandatory takes
the singular prefix; to wit, $. What's next? Integer and float and
complex and string and char and bits prefixes?
(Weighing in with the
18 matches
Mail list logo
