rs all
seem to be in flagrant disagreement with you.
In short, if foo.bar eq www.foo.bar, someone has high-jacked port 53.
--tom
=
Austin Hastings
Global Services Consultant
Continuus Software Corporation
[EMAIL PROTECTED]
__
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/
the
$, @,
: and % characters?
:
: @foo = @a @+ @b;# element by element add
Because it's difficult to tell the operators from the terms visually.
Larry
=
Austin Hastings
Global Services Consultant
Continuus Software Corporation
[EMAIL PROTECTED
the
$, @,
: and % characters?
:
: @foo = @a @+ @b;# element by element add
Because it's difficult to tell the operators from the terms visually.
Larry
=
Austin Hastings
Global Services Consultant
Continuus Software Corporation
[EMAIL PROTECTED
Some of the objections have gone by, but what if you reverse the
quotes?
Make operator-in-quotes be a string operator (hell, make that true for
the other ops, too)
Perl 5 Perl 6
--- ---
- .
+ +
. +
eq = or eq
ARCHitecture and Stem Development --
http://www.stemsystems.com
Learn Advanced Object Oriented Perl from Damian Conway - Boston, July
10-11
Class and Registration info:
http://www.sysarch.com/perl/OOP_class.html
=
Austin Hastings
Global Services Consultant
Continuus Software Corporation
that the Clippy wasn't originally and truly
annoying? :-)
Something worthwhile and interesting?
A benefit to mankind?
ummm, Something that IBM or the Sun corporation would want to steal?
=
Austin Hastings
Global Services Consultant
Continuus Software Corporation
[EMAIL
is kind of lame...
=Austin
Consider it a given that we'll be using . for dereferencing.
(Possibly
with - as a synonym, just for Dan. :-)
Larry
=
Austin Hastings
Global Services Consultant
Continuus Software Corporation
[EMAIL PROTECTED
--- Dan Sugalski [EMAIL PROTECTED] wrote:
Oh, didn't Larry tell you? We're making perl's parser locale-aware so
it uses the local language to determine what the keywords are.
I thought that was in the list of things you'd need to take into
account when you wrote the parser... ;-P
mios
--- Dan Sugalski [EMAIL PROTECTED] wrote:
At 07:40 AM 5/16/2001 -0700, Austin Hastings wrote:
--- Dan Sugalski [EMAIL PROTECTED] wrote:
Oh, didn't Larry tell you? We're making perl's parser
locale-aware so
it uses the local language to determine what the keywords are.
I thought
--- Damian Conway [EMAIL PROTECTED] wrote:
It's probably just a matter of coding what you actually mean.
In Perl 5 and 6 your version means if $fh is true in *any*
possible way..., whereas you seem to want if $fh is defined,
which is:
Hmm. I can easily see this producing
--- Jarkko Hietaniemi [EMAIL PROTECTED] wrote:
On Fri, May 18, 2001 at 06:22:10AM -0700, Austin Hastings wrote:
Hmm. I can easily see this producing incomprehensible code when
spread
across large systems. To wit, those developers used to 0 means
false
Any feature is incomprehensible
--- Jarkko Hietaniemi [EMAIL PROTECTED] wrote:
Yes... if you are using only the true property. But assume func()
can attach either true or false to its return value (and in the
latter case, also the what_went_wrong property to indicate the
cause,
$retval.what_went_wrong(Gorkulator
That's not how I see it. The filehandle is naturally true if
it succeeds. It's the undef value that wants to have more
information. In fact, you could view $! as a poor-man's
way of extracting the error that was attached to the last
undef.
Hmm. Thus?
sub fuu()
{
my $retval is
Let it be.
Not a flame, but a suggestion:
let $pi be constant;
That any better?
=Austin
--- Dan Schmidt [EMAIL PROTECTED] wrote:
Peter Scott [EMAIL PROTECTED] writes:
| I've been reading is as a declarative imperative, something which
| declares a property of something you are
--- Garrett Goebel [EMAIL PROTECTED] wrote:
Then what's the use of using object methods to override properties?
It's funny that the discussion should go this way. From way back in the
beginning, I got the impression that properties were temporary hacks,
and object methods would be the
--- Dan Brian [EMAIL PROTECTED] wrote:
Correct. The benefit is not as obvious as some seem to think.
If the goal is format consistency, then what is gained by format
consistency? It hardly means that you could translate one language
to another, or have close interrelations between
Falling back on the numbers is strings, too legacy:
$a = 100;
$b = 000;
$c = ($a _ $b) + 1;
# I'd expect $c == 11.
If I say:
$a = 1 _ 000 _ 000;
or
$a = 1_000_000;
DWIM (In scalar context, coerce arguments to strings).
(Frankly, I think this is unlikely. But who knows?)
If course, if
It can't be that confusing at first glance if English dedicates a slot
way up in the huffman table to the word, eh?
print ;
if ($need_eol but $current_column 21);
OTOH, this might become an and grep-not operator for (was it
Damian?)'s quantum operators:
@y = all(@x) but { /^anti/ };
--- Larry Wall [EMAIL PROTECTED] wrote:
Simon Cozens writes:
: Larry Wall:
: Not the same concept exactly. I think a Cbreak within a Cfor
loop
: would be the same as a Cnext, not a Clast.
:
: Doesn't this break C and Shell resonance?
We've done that before. :-)
Umm, doesn't
The obvious extension to given value is given list, as:
given $foo - $bar is rw,# I think this is more readable
$moo - $baz is rw
{
...
}
or
given ($foo, $moo) - ($bar is rw, $baz)
{
...
}
What would the default-variable scheme do in this context?
(Please, no-one suggest
Currently,
given $foo - $bar
{
}
can be thought of as
foreach my $bar ($foo)
{
}
Given the way people with expectations will interpret break, setting
break === last seems like the right thing to do.
=Austin
--- Larry Wall [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] writes:
: --- Larry
In all my (not incredibly vast) experience with languages that offer
with type commands, I don't think I've ever actually been in a
situation where I wanted to eat just one. It has always been 'compare
hideously nested structure member A to correspondingly hideous table
data B' or some such.
And
More questions on downwards binding,
for @foo - $a, $b { # two at a time
...
}
Interpretation #1:
for @foo[0..$foo:2] - $a,
@foo[1..$foo:2] - $b
{ ... }
Interpretation #2:
for @foo - $a { $b := $a; ... }
I like this second one, as a short-cut, but it's not worth
The when keyword can use a localizer that makes its target obvious but
slightly counter-intuitive.
given $x {
when /a/ { ... }
}
The problem is operations within the when-block that might expect to
use $_, the defaultdefault variable.
given $x {
when /a/ { s/a/A/; }
}
After all, I used a
It's amazing what a night will do. See bottom.
--- Allison Randal [EMAIL PROTECTED] wrote:
On Tue, Feb 26, 2002 at 02:20:48PM -0800, Brent Dax wrote:
Austin Hastings:
#
# Which, then, would you like:
#
# To implicitly localize $_, losing access to an outer version,
# or to have
--- Larry Wall [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] writes:
: More questions on downwards binding,
:
: for @foo - $a, $b { # two at a time
: ...
: }
:
: Interpretation #1:
: for @foo[0..$foo:2] - $a,
: @foo[1..$foo:2] - $b
: { ... }
:
:
--- Garrett Goebel [EMAIL PROTECTED] wrote:
Larry Wall wrote:
I think the switch statement will have to recognize any
Class::Name known at compile time, and force it to call
$!.isa(Class::Name).
Don't you mean the case/when statement? Wouldn't you want the
following to
work:
for
--- Austin Hastings [EMAIL PROTECTED] wrote:
--- Garrett Goebel [EMAIL PROTECTED] wrote:
Larry Wall wrote:
I think the switch statement will have to recognize any
Class::Name known at compile time, and force it to call
$!.isa(Class::Name).
Don't you mean the case/when statement
--- Garrett Goebel [EMAIL PROTECTED] wrote:
Speaking of which, you forgot your trailing semicolon
for the Cwhen expression's final closure/block.
I'll claim that when, like if, shouldn't need one. (I'd also normally
use multiple lines, but I'm trying to conserve newlines... :-)
Why does
--- Allison Randal [EMAIL PROTECTED] wrote:
I'm still not convinced of your basic point, that it would be a good
thing to have Cwhen aliasing $_. Variations on whether it does it
automatically or at my request and how don't change the fundamental
concept. Cwhen is a conditional like Cif, not
--- Garrett Goebel [EMAIL PROTECTED] wrote:
Allison Randal wrote:
Garrett Goebel wrote:
I guess the next question in the context of the following is:
Larry Wall wrote in Apocalypse 4:
It should be possible to make user-extensible syntax look
just like built-in syntax.
--- Allison Randal [EMAIL PROTECTED] wrote:
On Wed, Feb 27, 2002 at 10:11:13AM -0800, Austin Hastings wrote:
Cwhen is a conditional like Cif, not a topicalizer.
Right, it's a topicalizee, the victim of topicalization.
And so it uses $_ or $x or $! or whatever the current topic
--- Bart Lateur [EMAIL PROTECTED] wrote:
On Wed, 6 Mar 2002 17:57:07 -0500, Uri Guttman wrote:
how often will you need to interpolate a hash?
A whole hash: quite rarely. A hash item: a LOT. Don't forget that
$foo{BAR} will now become %foo{BAR}
Of course, it could also become %s. Or _
--- Larry Wall [EMAIL PROTECTED] wrote:
:
: 1a. Modules may be use-ed in several ways (syntax ignored for
now):
:
: # Note ...installed on this system is implied at the end
: # of each of the following descriptions
:
: Use the latest stable version of module Foo (probably
I think that if a package deliberately tries to untaint data, and then
the data isn't untainted, there will be an error shortly.
Perhaps you could be more specific about what you mean by untainting
things which shouldn't be untainted? Did you mean globals?
Otherwise, I'd think that if a package
--- Larry Wall [EMAIL PROTECTED] wrote:
On Sun, 13 Oct 2002, Michael Lazzaro wrote:
: My temporary hack while writing the proto-recipes was that we'd
have a
: property that would simply declare a method to be a class method,
but
: I'm having a hard time coming up with an acceptable name to
In 'C', we have:
a = b+c;
In Perl, we can have:
$a = $b$c;
(Parseable as $a = $b operator:spacespace operator:tab
operator:spacespace $c;)
Oh frabjous day!
=Austin
--- David Wheeler [EMAIL PROTECTED] wrote:
On Thursday, October 24, 2002, at 10:34 AM, Larry Wall wrote:
On
In the interest of email sanity, please make sure that neither Larry's
preferred : nor the more-common are valid at statement start...
I'd hate to stumble across
: - - like 'sub' ;
And run the risk of it compiling both as a quote and not.
=Austin
--- Larry Wall [EMAIL PROTECTED] wrote:
On
--- Michael Lazzaro [EMAIL PROTECTED] wrote:
'kay. As an aside, I've always itched for a qlike op that was
matrix-like, e.g.
my Pet @list = qm{
fido dog collie
fluffy cat siamese
};
That should be qo, and possibly @qo or qoo -- it quotes an object.
How about leave?
leave
SURROUNDING | [SURROUNDING]IDENTIFIER
[ [result] VALUE-SPEC ];
Aliases:
=
return - leave sub
exit - leave program (or is it thread?)
break - leave loop (this is shaky: does it deserve to be here?)
last - leave block
Extensions (these are WAY!
Since xor is really low frequency, why not make xor mean xor?
$zero = $a xor $a;
$a xor= $b;
$b xor= $a xor= $b xor= $a; # Swap'em
@a ^xor= @b; # Is this right?
=Austin
--- Larry Wall [EMAIL PROTECTED] wrote:
On Sun, 27 Oct 2002, Michael Lazzaro wrote:
: If \ meant xor, and some of the
Sorry, forgot to hit reply-all.
--- Austin Hastings [EMAIL PROTECTED] wrote:
Date: Mon, 28 Oct 2002 12:58:16 -0800 (PST)
From: Austin Hastings [EMAIL PROTECTED]
Subject: Re: labeled if blocks
To: Larry Wall [EMAIL PROTECTED]
--- Larry Wall [EMAIL PROTECTED] wrote:
On Mon, 28 Oct 2002
$accumulator += +X10;
Looks like hex arithmetic.
=Austin
--- Michael Lazzaro [EMAIL PROTECTED] wrote:
Okay, take 4, with 'X' meaning xor, so you can see it in context. I
warn ya, I'm gonna keep doing this until there's a Final version,
for
some value of Final. ;-) Again, I'm
If you guys start trying to reserve punctuation for XNOR, the next perl
cruise is going to be through the Bermuda Triangle...
=Austin
--- Jonathan Scott Duff [EMAIL PROTECTED] wrote:
On Mon, Oct 28, 2002 at 01:19:05PM -0800, Michael Lazzaro wrote:
On Monday, October 28, 2002, at 01:09 PM,
0x14 is questionably defined.
0X14 currently is an expression whose value is 14.
If we're going to kill the alternate radix literals, better to do
something like hex:123 or hex 123. I'd hate to try to comprehend
$a = -x:123;
more than a week from now. (Is it a negative hexadecimal number, or a
I think that endian issues are abstracted from literals. The place it's
going to be an issue is the specifiers for pack/unpack or whatever
replaces them.
But the presence of the operator (and speaking of low-frequency
operators, what about bitwise rotation? Will that be the (( and ))
operators?)
Didn't I see an operator list a while back that featured sign-extending
shift?
If not, I apologize.
But on the other hand, we could make a ~ operator that was a
case-preserving indent :-)
=Austin
--- Larry Wall [EMAIL PROTECTED] wrote:
On Mon, 28 Oct 2002, Austin Hastings wrote
--- Piers Cawley [EMAIL PROTECTED] wrote:
one(any($a, $b, $c), all($d, $e, $f))
Is a good deal more intention revealing than the superficially
appealing than
($a $b $c) ^ ( $d | $e | $f )
Would it be practical/meaningful to say
$result = bitwise ($a $b $c) ^ ($d |
[EMAIL PROTECTED] wrote:
On Tue, 29 Oct 2002, Austin Hastings wrote:
: --- Piers Cawley [EMAIL PROTECTED] wrote:
:
: one(any($a, $b, $c), all($d, $e, $f))
:
: Is a good deal more intention revealing than the superficially
: appealing than
:
: ($a $b $c) ^ ( $d | $e
Can we have a secret handshake, too? Will we be blamed for the secret
features of the new US dollar bill?
You know that eye-in-the-pyramid looking thingy? Well, notice what
character on the COMPUTER KEYBOARD that looks like? It's not by
coincidence that many of the programmers at the Treasury
I confess, I don't get it. To me, it appears to iterate over the input,
printing unique values except that two values ($start, $finish) are
considered to have already been encountered.
If that's all, then okay. But does it somehow skip all entries
before/after the delimiter?
Also, in a related
Interesting point, especially if operator:+= can be overloaded.
@a [+=] @b;
implies iteratively invoking operator:+=, whereas
@a [+]= @b;
implies assigning the result of iteratively invoking operator:+
It only matters when they're different. :-|
And, of course, if they ARE different then
--- Jonathan Scott Duff [EMAIL PROTECTED] wrote:
On Wed, Oct 30, 2002 at 09:13:02AM -0800, Austin Hastings wrote:
--- Jonathan Scott Duff [EMAIL PROTECTED] wrote:
Maybe we've gone over this before but, if so, I don't remember
...
On Tue, Oct 29, 2002 at 05:16:48PM -0800, Michael
--- Larry Wall [EMAIL PROTECTED] wrote:
On Wed, 30 Oct 2002, Austin Hastings wrote:
: No, no. I'm talking about the unary . prefix
:
:method blah {
: .foo()
: [.]foo() # What does this mean?
:}
:
: Vector of invocations of the foo methods
--- Larry Wall [EMAIL PROTECTED] wrote:
Do these French quotes come through?
@a «+» @b
Oui, M'sieu!
__
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
--- Dyck, David [EMAIL PROTECTED] wrote:
-Original Message-
From: Austin Hastings [mailto:austin_hastings;yahoo.com]
How do you write a in a Windows based environment? (Other than by
copying them from Larry's emails or loading MSWord to do
insert-symbol)
You could use
--- Damian Conway [EMAIL PROTECTED] wrote:
Austin Hastings wrote:
? ?| ?^ - [maybe] C-like bool
operations
?= ?|= ?^= - (result is always just 1 or
0)
[?][?|][?^] - (hyperversions
--- Damian Conway [EMAIL PROTECTED] wrote:
Larry wrote:
Possibly we might even extend the notion of hash to any junk.
%hash = 1 | 2 | 3;
So you're suggestion that a normal hash is a junction of pairs???
Damian Conway admits: Everything in Perl6 is 'Junk'
Who can't see *this*
--- Larry Wall [EMAIL PROTECTED] wrote:
On Thu, 31 Oct 2002, Markus Laire wrote:
The really great thing about the French quotes is that they visually
keep the user aware of the composition. «+=» is obviously a variety
of
+=, whereas ^+= is not obvious, though shorter. (Square brackets are
--- Luke Palmer [EMAIL PROTECTED] wrote:
And if you really want to drool at all the neat glyphs that the
wonderful, magical world of math has given us, check out:
http://www.unicode.org/charts/PDF/U2A00.pdf
now *theres* some brackets!
Ooh! Let's use 2AF7 and 2AF8 for
--- Luke Palmer [EMAIL PROTECTED] wrote:
--- Damian Conway [EMAIL PROTECTED] wrote:
Austin Hastings wrote:
traits = any ( ... )
requirements = .. ..
if $requirements eq $traits
Should that be traits = all()?
No. Because later we say (effectively):
print
This ¶ is a pilchrow, which shows up for me as one of those
paragraph-sign looking backwards P's with two vertical bars. Sorry if
it doesn't come out for you.
--- Brent Dax [EMAIL PROTECTED] wrote:
The Unicode version is more typing than the non-Unicode version, so
what's the advantage?
Something from [EMAIL PROTECTED] about the relative frequency made me
wonder:
What's the order of evaluation or nestedness for separate streams
in a for loop?
That is, can I meaningfully say:
for my $i; $j - 0 .. @array.length - 1; $i + 1 .. @array.length
{
..
}
And get the equivalent of two
--- [EMAIL PROTECTED], UNEXPECTED_DATA_AFTER_ADDRESS@.SYNTAX-ERROR.
wrote:
Mmm, I view one-character Unicode operators as more of an escape
hatch
for the future, not as something to be made mandatory. But then,
I'm one of those ugly Americans.
EBCDIC didn't support brackets, originally, so
--- Luke Palmer [EMAIL PROTECTED] wrote:
I don't know where to correct you first... :)
Is that a dunce-hat? Is there an ISO version I could use instead? :-
I'll start by saying your variables are on the wrong side of the
pointy sub. Also, presuming you switched the order, that Cmy
--- Ken Fox [EMAIL PROTECTED] wrote:
Austin Hastings wrote:
The question is not about being ISO-phobic or pro-English. **
The two gripes I've heard have been:
1- It's hard to type.
2- I don't know how to type it on platform X.
With combo gripe It'll be hard to remember how to type
--- Me [EMAIL PROTECTED] wrote:
people on the list who can't be bothered to read
the documentation for their own keyboard IO system.
Most of this discussion seems to focus on keyboarding.
But that's of little consequence. This will always be
spotted before it does much harm and will
--- Brian Ingerson [EMAIL PROTECTED] wrote:
FWIW, ebcdic *does* have the cent sign!
And the not sign. Damian may force us to abandon ASCII entirely...
=Austin
__
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
--- Rafael Garcia-Suarez [EMAIL PROTECTED] wrote:
Austin Hastings wrote in perl.perl6.language :
What we've got is an encoding problem at the MUA level. Mark Reed
says
my mailer (Yahoo!) tagged a message containing high-bit characters
as
US-ASCII. Several people the other day reported
--- Simon Cozens [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Austin Hastings) writes:
Yeah, but ActiveState does Perl, and Microsoft owns ActiveState
To what extent are *either* of those statements true? :)
Hmm. Well, last time I checked you could still download a perl binary
from
--- Adam D. Lopresto [EMAIL PROTECTED] wrote:
I'm having trouble this is even being considered. At all. And
especially for these operators.
Heute vektoren, morgen das welt!
Uniperl, Uniperl uber alles,
Uber alles in der welt!
With hyper-states through choose and true();
Masterfully golf
I think Damian already covered this: it's the semicolon.
sub mysub(String $content; int $key, int $align)
{
...
}
sub callmysub
{
mysub(Testing .. 1, 2, 3!; key = 1024, align = Module::RIGHT);
}
Which, upon reflection, apparently introduces an implicit hashparsing
context for autoquoting
--- Buddha Buck [EMAIL PROTECTED] wrote:
I think that if there were a slice-based form of grep, it would most
likely look like you are indexing by a subroutine (or method)
reference
that takes no arguments other than an element of the array.
Something like:
@a = @grades[{$^x 90}];
--- Michael Lazzaro [EMAIL PROTECTED] wrote:
Primitive types were originally intended for runtime speed, thus an
int or a bit is as small as possible, and not a lot of weird
runtime
checking has to take place that would slow it down. It can't even be
undef, because that would take an extra
--- Piers Cawley [EMAIL PROTECTED] wrote:
I wonder what would happen if you had a junction of
continuations. Producing something practical is left as an exercise
for the interested reader.
Isn't this effectively paste(1) ?
That is,
my $outfh = all(@input_handles);
while ($outfh) print;
--- Piers Cawley [EMAIL PROTECTED] wrote:
Austin Hastings [EMAIL PROTECTED] writes:
--- Piers Cawley [EMAIL PROTECTED] wrote:
I wonder what would happen if you had a junction of
continuations. Producing something practical is left as an
exercise
for the interested reader.
Isn't
--- Damian Conway [EMAIL PROTECTED] wrote:
The semantics of Cfor would simply be that if it is given an
iterator object (rather than a list or array), then it calls
that object's iterator once per loop.
By extension, if it is NOT given an iterator object, will it appear to
create one?
That
--- Damian Conway [EMAIL PROTECTED] wrote:
Austin Hastings asked:
That is, can I say
for (@squares)
{
...
if $special.instructions eq 'Advance three spaces'
{
$_.next.next.next;
}
...
}
or some other suchlike thing that will enable me to consistently
--- Damian Conway [EMAIL PROTECTED] wrote:
Iain 'Spoon' Truskett wrote:
@a ???+??? @b
@a ???+??? @b
Y'know, for those of us who still haven't set up Unicode, they look
remarkably similar =)
Think Of It As Evolution In Action
;-)
This coming from someone whose national
Larry wrote:
So you can do it any of these ways:
for $dance {
for $dance.each {
for each $dance: {
^ note colon
1- Why is the colon there? Is this some sub-tile syntactical new-ance
that I missed in a prior message, or a new thing?
2- Why is the colon
So what's wrong with:
sub foo($param is topic //= $= // 5)# Shorter form with $=
sub foo($param is topic //= $CALLER::_ // 5)
It doesn't really seem like we can make it much shorter. Yes, we could
convert //= into a single character, but why? People will understand
//=.
The idea of $= as
--- Allison Randal [EMAIL PROTECTED] wrote:
Larry wrote:
I'm trying to remember why it was that we didn't always make the
first
argument of any sub the topic by default. I think it had to do
with
the assumption that a bare block should not work with a copy of $_
from
the outside.
--- Allison Randal [EMAIL PROTECTED] wrote:
On Tue, Nov 19, 2002 at 01:24:30PM -0800, Austin Hastings wrote:
So what's wrong with:
sub foo($param is topic //= $= // 5)# Shorter form with $=
sub foo($param is topic //= $CALLER::_ // 5)
It doesn't really seem like we can make
--- Deborah Ariel Pickett [EMAIL PROTECTED] wrote:
Ah . . . one message with two things I wanted to talk about. Good.
Allison wrote:
On Tue, Nov 19, 2002 at 01:24:30PM -0800, Austin Hastings wrote:
So what's wrong with:
sub foo($param is topic //= $= // 5)# Shorter form
--- Larry Wall [EMAIL PROTECTED] wrote:
...
This might work now, presuming
sub foo (;$_ = $=)
(or whatever) is really a binding, and not an assignment. (That's
another reason why //= is *wrong*--it implies assignment.)
Umm, that's what it was supposed to do.
IOW: sub($param //=
They can't be very serious -- the archive link is dead.
Or perhaps everyone agrees that something needs to be done, but no-one
has any ideas?
=Austin
--- Joseph F. Ryan [EMAIL PROTECTED] wrote:
david wrote:
The brazen heresy continues...
Explain how having indexes (arrays, substr, etc...) in Perl 6 start
at 0 will benefit most users.
The languages which do not start their indices at 0 are dead or dying.
Do not invoke legacy.
How about FUD? :-)
=Austin
--- Michael G Schwern [EMAIL PROTECTED] wrote:
I'm going to ask
In thinking about how to write a partition function (or separate, or
whatever you want to call it) it occurs to me that you might want some
sort of reverse-varargs behavior, like
my (@a, @b, @c, @d) = @array.partiton { $_ % 4 };
So in this case, partition is supposed to determine, on the fly,
--- Dave Whipp [EMAIL PROTECTED] wrote:
I think that ccull would be an abysmal name: that implies
keep the false ones. I'm not sure that there is a synonym
for boolean partition though. Perhaps we need some help
from a linguist! ;)
What's wrong with split()?
split { f($_) }, $iterator
--- Adam Turoff [EMAIL PROTECTED] wrote:
On Mon, Dec 09, 2002 at 08:36:20PM -, Smylers wrote:
Perhaps there are only some edge cases which require calculation;
or the function is liable to be called with many invalid input
values, which can quickly be determined yield Cundef and so
--- Paul Johnson [EMAIL PROTECTED] wrote:
On Mon, Dec 09, 2002 at 01:58:11PM -0800, Austin Hastings wrote:
Ahh. This is better. How does one implement a more sophisticated
cache management strategy?
That is, what is the mechanism for manipulating the run-time system
behavior of subs
--- Dave Whipp [EMAIL PROTECTED] wrote:
We seem happy to structure objects (using
attributes, etc.), but verbs remain flat and uninteresting: just
arbitrary names.
As a result of this lack of expressiveness in the grammar, we find
ourselves saying that if a concept doesn't fit the
--- Piers Cawley [EMAIL PROTECTED] wrote:
Both of your proposed options are, frankly, vile. The
multimethod/generic function approach has the advantage of putting
the
'burden' of writing the generic function on the implementor rather
than on the user. Given that implementation happens
--- Dave Whipp [EMAIL PROTECTED] wrote:
I can imagine writing:
$a eq:i $b # compare, case insensitive
$a eq:w $b # compare, ignore whitespace differences
$a eq:ID $b # compare identities
I think that the modifier concept is too useful to be limited to the
rx// operator. But there
--- Damian Conway [EMAIL PROTECTED] wrote:
@out = @a ~ grep {...} ~ map {...} ~ sort;
...
@out ~ sort ~ map {...} ~ grep {...} ~ @a;
That way, everything is still a method call, the ultra-low precedence
of
~ and ~ eliminate the need for parens, and (best of all)
--- attriel [EMAIL PROTECTED] wrote:
I'm not even sure how that would parse, though that:
@keep ~ grep /good/ ~ @list ~ grep /bad!/ ~ @throw;
would go like:
( @keep ~ grep /good/ ~ @list ) ~ grep /bad!/ ~ @throw;
which is probably not what i wanted...
I would, from the
--- Jonathan Scott Duff [EMAIL PROTECTED] wrote:
On Wed, Jan 08, 2003 at 05:14:06PM +0100, frederic fabbro wrote:
I'm not even sure how that would parse, though that:
@keep ~ grep /good/ ~ @list ~ grep /bad!/ ~ @throw;
would go like:
( @keep ~ grep /good/ ~ @list ) ~ grep /bad!/ ~
--- Mr. Nobody [EMAIL PROTECTED] wrote:
--- Thom Boyer [EMAIL PROTECTED] wrote:
Mr. Nobody [EMAIL PROTECTED] wrote:
--- Damian Conway [EMAIL PROTECTED] wrote:
@a ~ grep {...} ~ map {...} ~ sort ~ @out;
That's going to be just plain confusing. Arguments to functions
are
--- attriel [EMAIL PROTECTED] wrote:
Could someone explain how to know what's the indirect object? (who
knew
the sentence diagramming would be USEFUL!!)
Short version:
If there's two people in the sentence, the verb-ee is either the direct
or indirect object. If there's two people and a
--- Mr. Nobody [EMAIL PROTECTED] wrote:
--- Buddha Buck [EMAIL PROTECTED] wrote:
Mr. Nobody wrote:
Unicode operators in the core are a very, very, very, very, very,
very,
very,
very, very, very, very, very, very bad idea.
We've already had this discussion. We wouldn't be
1 - 100 of 451 matches
Mail list logo
