On Fri, 2002-07-12 at 13:22, Thomas A. Boyer wrote:
> Aaron Sherman wrote:
> > An example:
> >
> > $pid = fork() // -1;
> > if $pid < 0 {
> > # error ...
> > } else unless $pid {
> > # Parent
> > } else if $pid > 0 {
> > # Child
> > } else {
> >
On Monday 15 July 2002 07:52 am, Brent Dax wrote:
> Ashley Winters:
> # > You've got a point. There's an easy way to say "I want a sub":
> # >
> # > my $sub = -> { ... }
> # >
> # > But I can't think of a similarly punctuation-intensive way
> # to say "I
> # > want a hash." (someone please step
Ashley Winters:
# > You've got a point. There's an easy way to say "I want a sub":
# >
# > my $sub = -> { ... }
# >
# > But I can't think of a similarly punctuation-intensive way
# to say "I
# > want a hash." (someone please step in and correct me).
#
# I nominate:
#
# $() == scalar()
# %()
On Monday 15 July 2002 06:57 am, Sean O'Rourke wrote:
> On Sun, 14 Jul 2002, Brent Dax wrote:
> > Deborah Ariel Pickett:
> > # My perl5 sensibilities tell me that that's likely to cause a
> > # problem when I want to do something like this:
> > #
> > # $hashref = { function_returning_hash() };
> >
On Sun, 14 Jul 2002, Brent Dax wrote:
> Deborah Ariel Pickett:
> # My perl5 sensibilities tell me that that's likely to cause a
> # problem when I want to do something like this:
> #
> # $hashref = { function_returning_hash() };
> #
> # because I won't get the function's return values put into a
Deborah Ariel Pickett:
# [no longer sent to perl6-internals because it's not relevant there]
#
# I see a problem . . whether the problem's with me or the
# grammar, that's for you people to decide.
#
# Do I read this part of the grammar correctly?
#
# > sv_literal: /(?:\d+(?:\.\d+)?|\.\d+)(?
[no longer sent to perl6-internals because it's not relevant there]
I see a problem . . whether the problem's with me or the grammar, that's
for you people to decide.
Do I read this part of the grammar correctly?
> sv_literal: /(?:\d+(?:\.\d+)?|\.\d+)(?:[Ee]-?\d+)?/
> | '{' h
At 11:33 PM -0700 7/11/02, Sean O'Rourke wrote:
>It's time for my weekly post to this old thread. The grammar has
>grown enough to deserve more than one file, and is starting to change
>in new directions. For example, it's now Turing-complete, if you have
>a Parrot engine and a bit of spare time
Aaron Sherman wrote:
> An example:
>
> $pid = fork() // -1;
> if $pid < 0 {
> # error ...
> } else unless $pid {
> # Parent
> } else if $pid > 0 {
> # Child
> } else {
> # Huh? Can't happen
> }
Of course, your indentation implies a differen
On Fri, 2002-07-12 at 02:33, Sean O'Rourke wrote:
> What's currently "supported":
> - if/elsif/else (even "unless" and the feared "elsunless";)
When we talked about this last, I had been concerned about loops and
conditionals, but others had scoping concerns. Ok, perhaps there's no
way we can r
It's time for my weekly post to this old thread. The grammar has
grown enough to deserve more than one file, and is starting to change
in new directions. For example, it's now Turing-complete, if you have
a Parrot engine and a bit of spare time. Call it a primitive "demo
version" of some of Per
11 matches
Mail list logo
