MES
@foo = split; pop @foo until $foo[-1];
@foo = split ' ';
# BECOMES
@foo = split /\s+/; shift @foo;
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
thin a closed-off little clique.
What community needs do you feel are being ignored?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
rove :-) to be up in arms about it.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
uture tasks they may want to do and if they really want to
apprentice in this area.
my two cents,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
uld have
to outline things, of course, but anybody could fill in the details.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
for? Do you want
the default behavior of the RE engine to change and if so, how would
we get the current behavior?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
t; in 5.7 mergesort by John Lindermann was introduced.
Could someone give me a pointer to the whys and wherefors of the
change from quicksort to mergesort?
thanks,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
assumption that perl's sort
would be stable when, of course, it's not. Had perl 5.7 come along
sooner I might never have caught the bug or been bitten by it :-)
thanks again,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ting of lists?
http://dev.perl.org
All will be made clear there.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
'ftp://my.local.domain/perl-modules/Baz', VERSION => 2 };
Here are some questions:
* Is @INC searched prior to attempting to fetch the module via the URL?
* If so, what happens if there is higher version in @INC?
* What happens when the module isn't found?
* What happens when the requested version isn't found?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
while possibly helping some.
Perhaps. Except that you also propose to burden the language with two
new keywords.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ady have a switch that means "quick and dirty", it's called
"-e"
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
en and where to use parentheses is
part of the learning curve. This is a Good Thing.
MHO,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
irst reaction was that Larry had gone insane
when I saw that http://... example. But let him digest those beans
completely and we'll see what he comes up with.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Fri, Apr 06, 2001 at 03:32:56PM -0400, John Porter wrote:
> Jonathan Scott Duff wrote:
> > Doesn't look like another namespace, but rather an extension of an
> > existing one to me.
>
> An extension of a namespace? What's that?
> Either "modifiers&qu
s concerned; whatever it wants to
> do should be completely independent of any perl 6 code.
So ... when a "perl6" program uses a "perl5" library, what happens?
If we go with Larry's rule that a package declaration unambiguously
says you're parsing perl 5, then this situation WILL exist.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Tue, Apr 24, 2001 at 12:29:23AM -0700, Russ Allbery wrote:
> How do you concatenate together a list of variables that's longer than one
> line without using super-long lines?
join '', $var1, $var2, $var3, ..., $varN;
TMTOWTDI, remember.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
t($foo); # or something
Is concatenation really so important that we keep it around and not
only that, but break other things to keep it around?
(Obviously I think using . for objects is important enough to break
concatenation)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
to let Larry design the language, otherwise
we'd be mired in muck like this for a long time.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
Oh, and you need to relax your "Always" a bit.
"string" + $foo # string concat
$foo + "string" # string concat
Quotes around $foo shouldn't be necessary.
As an aside, I wish we could do something like this with our comparators
too. (Isn't that one of Damian's RFCs?) Although I get the feeling
that this will cause more headaches.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
t;good" means to you. We could give reasons all day long and you
could reply with "those aren't GOOD reasons".
How about this one: Because Larry said so.
Seems good enough to me.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
tion that doesn't
already have some well-established-across-multiple-languages meaning.
anyway, my two cents ...
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
lurps, %b gets nothing
(%a, *%b) = (%c,%d);# %a = %c, %b gets the rest
I'm sure your imaginations can twiddle the cardinality knob
appropriate for generalization :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
value
> properties, especially when you temporize a variable:
I think you've said something really profound here :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
TW, I've decided to stop calling them variable and value properties
because that terminology is just too confusing (for me at least). I like
"compile-time properties" and "run-time properties" much better.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Mon, May 21, 2001 at 12:47:15PM -0700, Dave Storrs wrote:
> On Mon, 21 May 2001, Jonathan Scott Duff wrote:
> > Would you also advocate separate declarative syntax for variable
> > properties and value properties? That's where I think much confusion
> > will be.
>
s 'arf'
and a 1 in the A column means $spot has a bark value (run-time) property
that says 'yip'.
MVA $spot.bark (+$spot).bark
000 Error Error
001 yip yip
010 arf Error
011 arf yip
100 woofwoof
101 woofwoof
110 woofwoof
111 woofwoof
yes?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
oposed how you can clear a user-defined
> property on a value?
delete $foo.prop{name};
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
gt; profiler?
What do you mean by "core" here? There is already a profiler provided as
one of the standard modules (which will presumably be part of perl6).
Are you suggesting that there should be language hooks for profiling
built into perl rather than as a module?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
rl gets reduce()
$select = reduce {
$_[0].qq{$_}
} '', @ary;
or whatever makes you happy.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
signature syntax to see what works and what
doesn't. (At this point, I'm *really* glad the language design is taking
years) Because of this there will be times when all of the guts are
exposed, but I don't think that it'll always be that way. By the time
perl 6.0.0 rolls around, the guts should be tucked away nicely.
my two cents,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ion of the "property" (just reusing the name from
subversion) names is up to whoever generates/consumes them, so they
could be anything
#language perl
#version 6
#file hello.p6
#line 1
#source say "hello world\n";
#chapter 4
#verse 7
#scoundrel Bill Sikes
... PIR that implements the HLL ...
etc.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
m with
it that I see is that you need to use @y[] to interpolate an array
into a string:
my $x = 0; my @y = 1..9; @y[$x++]++; print "$x\n"; print "@y[]\n"
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ot;parse perl".
The same holds for parsing perl6 only the twisty maze isn't there (or is
at least much much smaller)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
# or [0,2] or just [0] for that matters!
> # $s='cc';
> # @a=qw/aa bb dd ee/; => same as what I can do with slice()
>
> Not terribly necessary, but indeed consistent IMHO.
Not quite sure why you'd want this, but if we have something like this:
my @a = qw/aa bb cc dd ee/;
my @slice := @a[0..2];
my $s = pop @slice;
(where @slice is a "reference" to part of @a)
You get what you want and more.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ting regex results in
> a single-item list containing the original string. This is the Python
> behavior.
>
> I find the Perl5 (and, surprisingly, Ruby) behavior rather counterintuitive.
FWIW, I agree with Mark.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
position time (possibly by
failure)? That doesn't sound like debugging hell to me, but rather
clear indication of a problem and the location of that problem.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Wed, Jan 25, 2006 at 11:37:42AM -0800, Larry Wall wrote:
> I've changed the flipflop operator/macro to "ff", short for "flipflop".
Two questions:
1) Will ff (and fff) require whitespace around them?
2) Do we get a more punctuationish unicode equivalent?
-Scott
--
pmichaud says, it doesn't differ
substantially from what you've already seen.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
mit that Damian's brain doesn't work like everyone
> else's brain.
Just as another data point, I too have been thinking of "say" as "print
+ newline".
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
$x is 5 again
>
> and otherwise pretty much DWIMs, except from a historical
> perspective.
Is there some reason we're huffmannizing
my $x = 5;
{
temp $x = $MY::x + 1;# or whatever the proper syntax is
# $x is 6
}
$x = 5;
??
Can you elaborate an example that wou
On Mon, Mar 27, 2006 at 10:46:02PM +0200, Yuval Kogman wrote:
> On Mon, Mar 27, 2006 at 14:35:52 -0600, Jonathan Scott Duff wrote:
> > I think that if C is the new C, then immediately after the
> > C line, $x should hold whatever flavor of undef is appropriate.
> >
> >
Perl6 do I need Pugs ? I understood I would
> need only the new Parrot VM ? Isn't that right ?
Eventually. When there's a perl6 compiler that's based on parrot.
Right now, the only usable implementation of perl6 that we have is
pugs.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
and hoping we notice when things change?
Sending the log + diff gives an easy way to brain-filter the messages
too. I can look at the log and decide if I really care about the minute
changes to twigils enough to read through all of the places where it
makes a difference.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Sat, Apr 08, 2006 at 03:22:15PM -0400, Sean Sieger wrote:
> Is there public access to the synopses at svn or cvs?
If you're just looking for read-only access, see
http://svn.perl.org/perl6/doc/trunk
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
tern /;
is very much the same as
state $x; $x = $x || /pattern/;
I'd say that's a "boolean context" and thus matches against $_ instead
of assigning the Regex object to $x.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Fri, Apr 21, 2006 at 11:06:20AM -0700, Larry Wall wrote:
> On Fri, Apr 21, 2006 at 12:45:13PM -0500, Jonathan Scott Duff wrote:
> : According to S05, "a /.../ matches immediately in a value context
> : (void, Boolean, string, or numeric)" and since
> :
> :
he first place.
Why would you need to match the key again? Maybe your subrule needs to
know what came before the key in order to perform some action:
req() if m:c/ / # require
des() if m:c/ / # desire
I assume that is somehow magically anchored to the spot where
the key actually matched.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
7;s no easy way to say "match 1, 7, 12, or
19" with this particular syntax.
How often does that come up in practice though? I don't think I've
ever wanted something like that.
If we allow "Junction of Int" that also gets us "Set of Int" as
Junctions are just funny Sets. Why not "Array of Int" too?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
didn't specify. My
vote would be that list([+] 1) == (1) just like [+] 1 == 1
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
t "may only" really
meant "must")
And if we're keeping the correspondence between classes+methods and
grammars+rules, then surely grammars are composable entities just
like classes.
Seeking clarification,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Thu, May 11, 2006 at 12:19:21PM -0700, Allison Randal wrote:
> Jonathan Scott Duff wrote:
> >On Wed, May 10, 2006 at 05:58:57PM -0700, Allison Randal wrote:
> >>rule:
> >>- Has :ratchet and :skip turned on by default
> >>
> >>- May only b
he way to go.
Binaries are definitely worth it to give people something to play with
(especially on difficult platforms like Windows). It doesn't have to be
the latest and greatest, it just has to implement a large-enough
feature set.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
win32) separated list of directories to search.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
t). If you're going to type @results, maybe it needs to be:
my @results is Array of Array of int;
or maybe
my Array of int @results;
Or something like that :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
if there's a way to order
> >the locks in virtual time such that they still make sense. Then you
> >just pretend that things happened in that order.
>
> Forgive this ignorant soul; but what is "STM"?
Software Transaction Memory
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
nstant = 0;
> my Int $b is constant = 0;
> (cond(True, $a,$b))++;
We have a "constant" declarator now, so that would be
constant Int $a = 0;
constant Int $b = 0;
(cond(True, $a,$b))++;
and that should fail at compile time because the compiler knows that
$a and $b are constant and can't be rw.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
x27;d need to be explicit:
talk(~123,3);
But I'm not sure which way perl6 actually leans.
Though it seems to me that automatic type conversion by the compiler is
a way to get yourself in trouble. Not that perl shouldn't let the
programmer get himself in trouble, but this seems like one of those
things that should require asking to turn on rather than asking to
turn off.
my two cents,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Fri, Jun 23, 2006 at 06:55:28PM +0300, Markus Laire wrote:
> On 6/23/06, Jonathan Scott Duff <[EMAIL PROTECTED]> wrote:
> >An alternate interpretation would be that the last one is actually a
> >compile-
> >time error because none of the sigs match (Int,Int) and f
ument type
appears in the "does list" of the Signature, then it's a match and all
is well. Otherwise it's an error. Since "Num does Int", a call such
as C succeeds.
At least that's my vague interpretation of this aspect of perl6 at
this moment. :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ffect of parameterized rules, you should really be using a
closure anyway?
So, I guess that answers your question ...
If not, I'm sure someone else will come along and give something more
definitive :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
you are generating may be
large (like say, between a very complex and rich language like Perl6 and
a much simpler language like PIR ;). TGE lets you factor out the
complexity of your source language in incremental steps (as small or as
large steps as you want).
> Good luck for today's presentation :)
Yeah, good luck Pm :)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
t has an indirect dependency on
> Devel::Caller which fails to work using that compiler combination (i.e.,
> fails all tests after a build using its makefile and Visual Studio 2003 as
> the C compiler).
Bummer. You could check out the Vanilla/Strawberry Perl effort at
http://win32.p
s that true? By the rules of hyper-operation, it turns into
this:
[1,2] ~~ sub { return 1 }
3 ~~ sub { return 1 }
which is true if these return true values:
sub { return 1 }->([1,2])
sub { return 1 }->(3)
Which they do.
So, smart-match fails as a "deep equality" operator precisely
because it's so smart.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
py;
eat :if $hungry;
go_postal :when $aggravation > 10;
.sleep :until .rested;
*Everybody* wants the colon! ;-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
7;re being required or
not because the "trick" is built-in to the language :)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
t do we do with the combinatorial explosion of this?
use Foo-(1.2 .. 3.3)-(X|Y|Z);
Suddenly it seems like a really good idea to only have one authority.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
le, it keeps it's
value between invocations, so the output would be:
42
43
# again, blank on purpose
1
> for 1,2 -> $x {
> END { say $x }
> }
For this one I'd guess that a solitary "2" is output. The END block
closed over the $x and the last value that $x obtained was 2.
my humble guesses,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
ne whether to call NEXT or LAST.
> (Sorry for the double post.)
Depends on when it fires I guess. Your example might be equivalent to
this perl5ish:
while (1) {
$num = rand;
print $num;
last if $num < 0.9;
print ","; # NEXT
}
print "\n"; # LAST
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
an create tools to deal with it (uuencode anyone?). Also by not keeping
to 80 columns, we can weed out the modern tools that still have such
limitations and encourage the authors to fix them. And if *that* turns
out to be too big of an endeavour, we can always go back to 80 columns,
but I'm guessing whatever problems there are will be small and
localized.
just my humble opinion,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
? This seems like something we shouldn't encourage as it
tends toward tight coupling of implementations where it should be
tight coupling of abstractions.
I don't know ... someone argue my brain into a new position :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
gs
better. Et cetera.
Does she also have some problem with perl5? It sounds like she's
just trying to apply the "perl is line noise" argument but only for
perl6. IMHO, the same counter arguments apply.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
scope lasts beyond the bounds of the block in
which it's executing so that things like
for @array { ... last if ...; }
say "Stopped processing at $=.index";
work.
But, again, we have other ways of making this work that don't involve
introducing some implicit thing.
-Scott (PerlJam)
--
Jonathan Scott Duff <[EMAIL PROTECTED]>
>
> Does making it all upper caps really help? It's still a pollution of the
> method space, any way that you look at it...
Yeah but perl has already has a cultural claim on ALLCAPS thingys.
So, yes, it does help.
-Scott
--
Jonathan Scott Duff <[EMAIL PROTECTED]>
ter all :)
Or maybe -e and friends are just macros and there are no postfix
forms.
-Scott
--
Jonathan Scott Duff <[EMAIL PROTECTED]>
g-name than
$some_long_name if only to not touch the shift key :-)
-Scott
--
Jonathan Scott Duff <[EMAIL PROTECTED]>
e, no more aliases. They only create confusion.
Sure, but "all's fair if you predeclare". Aliases imposed on us all may
cause confusion, but presumably, if an individual has asked for an
alias, they are willing to risk the potential confusion.
For me personally, I can live with "filter" as an alias for "grep".
But that's just me.
-Scott
--
Jonathan Scott Duff <[EMAIL PROTECTED]>
obj.$bar() # a method variable
The same could be used for ordinary subroutines:
.local string mysub
mysub = "foo"
$mysub()# calls the foo subroutine
-Scott
--
Jonathan Scott Duff <[EMAIL PROTECTED]>
into a Foo.
I'm of the opinion that if you need a routine to handle multiple
"types" then you should define it such that it is sufficiently general
enough to do so without the benefit of added behind the scenes magic.
-Scott
--
Jonathan Scott Duff <[EMAIL PROTECTED]>
nguage is still being designed, you
probably want to know about Perl5 resources. A good place to start
would be http://learn.perl.org/. Also, you might want to try on IRC.
There's #perl on the freenode network and #perlhelp on efnet.
hope this helps,
-Scott
--
Jonathan Scott Duff <[EMAIL PROTECTED]>
athematical behavior from Perl. Perhaps it's that you've been using
computers too long and have become used to the limitations of digital media.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
I accidently sent this just to Darren ...
-Scott
-- Forwarded message --
From: Jonathan Scott Duff <[EMAIL PROTECTED]>
Date: Jan 22, 2007 6:23 PM
Subject: Re: Numeric Semantics
To: Darren Duncan <[EMAIL PROTECTED]>
On 1/22/07, Darren Duncan <[EMAIL PROTECTE
that tends to muddy the waters a bit when
it comes to your brain helping you find the bug. (at least it does for me)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
e Pascal or Fortran programmers start all of their
arrays at something other than 0. And I can see the need for a modifier so
that an individual array can start at an index other that 0.
just registering my tuppence,
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On 2/6/07, Smylers <[EMAIL PROTECTED] > wrote:
Jonathan Scott Duff writes:
> ... I can see the need for a pragma to help out the Pascal or Fortran
> programmers start all of their arrays at something other than 0.
Those sort of crutches in programming languages (let's help f
// DO NOT EDIT THIS FILE - it is machine generated -*- c++ -*-
So, perhaps it's not the .h files we should be parsing, but whatever source
files were used to generate them. Though, of course, some C++-to-Perl6 tool
would be a good thing too. :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
$oldpos = pos $matchobj;# or just ...
$oldpos = pos; # uses the most recently seen
# match object
?
End of random ramblings ...
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
$quote }
$justtheword = //;
And if the above works, why can't "$var:=atom" be a short hand for a
lexical "rule var { atom }" that only applies for the current ... um ...
rule/? And thus the capture would be out
of band WRT $1, $2, etc. or the rule's return value.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
of match objects? Or some polymorhpic thing that can be either?
Would something like this work?
rule max ($pat) {
$0 := {
reduce { length $^a > length $^b ?? $^a :: $^b } <:a $pat>;
}
}
"bacamus" =~ m//;
-Scott
--
{ my $other;
rule leftop($leftop,$op;$rightop) {
{ $other = (defined $rightop) ?? $rightop :: $leftop }
<$leftop> [$op <$other>]*
}
}
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Sat, Jun 15, 2002 at 04:50:20PM +0200, Marcel Gruenauer wrote:
> On Sat, Jun 15, 2002 at 09:08:31AM -0500, Jonathan Scott Duff wrote:
>
> > At the very least you should be able to do this:
> >
> > rule leftop($leftop,$op;$rightop) {
> > $other := {
they are off hand. Maybe
my Date $bday = new Date 'June 25, 2002'; # or
my Date('June 25, 2002') $bday; # or
my Date $bday; $bday.new('June 25, 2002'); # or
# something else entirely.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
s) { ... }
then how does Perl know which constructor to call? Or would declaring
two constuctors like that cause Perl to carp at you? (I can't think
of a case where someone would want to have two constructors like that,
but I'm not letting my lack of imagination hinder this discussion :-)
Anyway, I think the method name should be required.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
gt; is actually syntactically illegal and you MUST
perform character class arithmetic as <[abc]+[def]>.
Somehow I prefer the former to the latter.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
t fails, $x is
restored to undef when the closure is backtracked
I don't see any binding there, just letting.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
proposing to *only* replace //=? Or are you proposing to
*only* replace //= in subroutine declarations?
What issues did you have with //=? It seems clear and concise to me.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
efault() to be synonymous with //= but only in
subroutine declarations. That seems a tad odd. Why not make it
synonymous everywhere?
my $foo is default(23); # same as ...
my $foo //= 23;
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
n the match object?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Wed, Sep 04, 2002 at 05:06:32PM -0400, [EMAIL PROTECTED] wrote:
> Is there a general rule that a property must make sense in all contexts?
Nah, I was just being distracted by work and not thinking clearly
about your default() proposal. :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
I hadn't been proceeding under any assumptions if I
could help it, but that's only because everytime I think I understand
the new perl6isms someone throws a kink in my understanding. :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
1 - 100 of 547 matches
Mail list logo
