On Tue, Dec 17, 2002 at 09:54:12AM +, Simon Cozens wrote:
[EMAIL PROTECTED] (Dave Storrs) writes:
Just so I'm clear, are you saying that you think L2R is a bad idea,
and should not be supported? Or just that it has not yet been
demonstrated that this is a good idea?
I think
On Tue, Dec 17, 2002 at 09:49:42AM -0500, Dan Sugalski wrote:
At 5:45 PM -0800 12/16/02, Dave Storrs wrote:
Just so I'm clear, are you saying that you think L2R is a bad idea,
and should not be supported? Or just that it has not yet been
demonstrated that this is a good idea?
I think it's
On Tue, Dec 17, 2002 at 09:54:52AM -0800, Michael Lazzaro wrote:
Umm... I think some of these recent messages have had typos between L2R
and R2L. (?) In that people seem to have been arguing against
themselves. (??) I'll try using -- and --.
Just to make sure I'm not one of those people,
On Tue, Dec 17, 2002 at 02:51:04PM -0500, Dan Sugalski wrote:
At 9:54 AM -0800 12/17/02, Michael Lazzaro wrote:
We _must_ (for some value of must that is real close to being a
100% drop-dead requirement) support -- (L2R), in the form of
@a.grep( {...} )
.map( {...} )
On Fri, Jan 03, 2003 at 10:58:49AM -0800, Mr. Nobody wrote:
--- Smylers [EMAIL PROTECTED] wrote:
junction should be sufficient:
print date if $var == any(1 .. 31);
Superpositions in the core? You're kidding, right?
What's wrong with if 1 = $var = 31?
My understanding was that
On Wed, Jan 08, 2003 at 08:31:51AM -0800, Austin Hastings wrote:
--- Damian Conway [EMAIL PROTECTED] wrote:
@out = @a ~ grep {...} ~ map {...} ~ sort;
...
@out ~ sort ~ map {...} ~ grep {...} ~ @a;
For the record, I think this is great.
Brilliant! Keep
On Wed, Jan 08, 2003 at 05:59:14PM +0800, Damian Conway wrote:
my Array @array := SpecialArray.new;
Should the value in @array act like an Array or a SpecialArray? Most
people would say SpecialArray, because a SpecialArray ISA Array.
Weell...*I'd* say that @array should act
On Sun, Jan 12, 2003 at 11:50:14AM +, Richard J Cox wrote:
U+21DC Leftwards Squiggle Arrow and U+21DE Rightwards Squiggle Arrow would
seem to fit the bill rather well maybe the ascii ~ and ~ are merely
aliases of the true symbols?
If we go this route, I would suggest that we use
On Thu, Jan 16, 2003 at 04:14:20PM -0600, Jonathan Scott Duff wrote:
On Thu, Jan 16, 2003 at 10:07:13PM +, Nicholas Clark wrote:
The headers I received make no mention of character set - does your mailer
mark the message in any way? If not, then STMP will assume it's good old
7 bit
On Fri, Jan 17, 2003 at 10:59:57AM -0500, Dan Sugalski wrote:
At 7:13 AM -0800 1/17/03, David Storrs wrote:
Do we at least all agree that it would be a good thing if Unicode were
the default character set for everything, everywhere? That is,
editors, xterms, keyboards, etc?
No. No, we
On Fri, Jan 17, 2003 at 12:19:01PM -0500, Dan Sugalski wrote:
At 8:08 AM -0800 1/17/03, David Storrs wrote:
On Fri, Jan 17, 2003 at 10:59:57AM -0500, Dan Sugalski wrote:
At 7:13 AM -0800 1/17/03, David Storrs wrote:
Do we at least all agree that it would be a good thing if Unicode were
On Fri, Jan 17, 2003 at 11:03:43AM -0800, Michael Lazzaro wrote:
And note that as pretty as - is, we couldn't have - for piping
because it would conflict rather strongly things like
if ($a-5)# (negative five, or pipelike?)
Pipelike. Longest token rule.
--Dks
On Fri, Jan 17, 2003 at 04:21:08PM -0800, Damian Conway wrote:
Paul Johnson wrote:
Well, I'll be pretty interested to discover what cause is deemed more
deserving than Larry, Perl 6 or Parrot. The P still stands for Perl,
right?
True. But I suspect that TPF's position is that, to many
On Tue, Jan 21, 2003 at 03:52:30PM -0800, Dave Whipp wrote:
$a = sub ($a, $b) { ... }
$x = - ($y, $z) { ... }
The pointy-arrow doesn't buy anything here.
IMHO, it's actually a loss. I have yet to come up with any mnemonic
for pointy arrow means sub that will actually stick in my brain.
Some random musings, for what they're worth...
1) The fact that we've had this long thread about arrays and shows
that they are confusing. How could we change the
functionality/eliminate the differences so as to simplify things?
2) It seems that the functionality of lists is a proper
On Fri, Feb 14, 2003 at 10:10:09PM -0700, Luke Palmer wrote:
Date: Fri, 14 Feb 2003 12:38:59 -0800
From: David Storrs [EMAIL PROTECTED]
Some random musings, for what they're worth...
1) The fact that we've had this long thread about arrays and shows
that they are confusing. How
On Wed, Feb 19, 2003 at 09:51:12AM +1100, Deborah Ariel Pickett wrote:
That said, I don't know of anything that the C comma operator can do
that you couldn't equivalently do with a Perl5 Cdo statement:
foo() or (do { warn(blah); next; }); # Yes, it's ugly.
Or just a Boolean:
foo()
Greetings all,
Ok, it took me several days to get through A6, and I'm not caught up
on all the mail yet (though I've tried to skim so I don't repeat
someone else's question). I'm left with a bunch of questions; can
anyone answer the following:
==QUESTION
- Page 8 says In some languages, all
On Sun, Mar 16, 2003 at 10:08:41PM -0500, Chris Dutton wrote:
On Sunday, March 16, 2003, at 05:09 PM, David Storrs wrote:
==QUESTION
- Page 8 says In some languages, all methods are multimethods. I
believe that Java is one of these. Is that right and what are some
others
On Sat, Mar 15, 2003 at 05:32:39PM -0500, James Mastros wrote:
On 03/14/2003 3:22 PM, Dan Sugalski wrote:
That means that TPF's perl development grant fund is fine to donate
to, and if there's only enough cash for one grantee, and Larry's the
best candidate, that's keen. Setting up a Fund
On Wed, Mar 19, 2003 at 12:19:20PM -0800, Michael Lazzaro wrote:
I think newbies are going to unquestionably try and put the parameters
in the same order as they expect to see the eventual arguments, and be
durn confused it doesn't work -- I know I would.
[...]
Dunno. I'm just one
I recently discovered a CPAN module called WhatIf
(http://search.cpan.org/author/SIMONW/Whatif-1.01/). This module has
the ability to provide rollback functionality for arbitrary code.
I don't really understand continuations yet (although I'm reading up
on them), so perhaps they would allow
time as short as
possible by clearly labelling everything.
David Storrs [EMAIL PROTECTED] wrote:
[re: current sig syntax]
In order to make it worthwhile (IMO), it would need to be very easy
to use, which would imply at least the following:
1) There are both long and short forms
On Fri, Apr 04, 2003 at 10:40:49AM -0800, Larry Wall wrote:
Yes, though it's usually been mentioned with respect to things like:
my ($a,$b,$c) is constant = abc();
However, I would personally go with the prefix zone macros before using
distributed traits, just to get the zone info out
On Wed, May 28, 2003 at 04:41:36AM -0600, Luke Palmer wrote:
I was reading about Haskell, and realized that I don't know what ::=
is supposed to mean (don't ask what that has to do with Haskell :-).
I know it's compile-time binding, but... what's compile-time binding?
Could someone who knows
On Wed, May 28, 2003 at 06:35:31AM -0700, David Storrs wrote:
On Wed, May 28, 2003 at 04:41:36AM -0600, Luke Palmer wrote:
I know it's compile-time binding, but... what's compile-time binding?
Luke
Well, perhaps I'm mistaken, but I had understood it to mean simply
[...]
- Named
So, as I sweat here in the salt mines of C++, longing for the
cleansing joy that Perl(5 or 6, I'd even take 4) is, I find myself
with the following problem:
Frequently, I find myself writing stuff like this:
void Ficp400::SaveRow(long p_row)
{
// if p_row is marked as deleted, return
On Thu, Jun 12, 2003 at 03:12:32PM -0700, Austin Hastings wrote:
sub Ficp400::SaveRow(Int $p_row)
{
return if IsDeleted($p_row);
}
*laugh* Well, yes, there is always the obvious way. I had wanted
something that would be reusable between multiple function, though
(sorry, should have said
On Tue, Jun 10, 2003 at 12:04:14PM -0700, Michael Lazzaro wrote:
J: (scalar junctive to typed scalar)
A scalar junctive, e.g. an untyped scalar, can always be silently
used as and/or converted to a more specific primitive type. This will
quite frequently result in the loss of
On Mon, Jun 16, 2003 at 02:09:43PM +0200, Edwin Steiner wrote:
Edwin Steiner [EMAIL PROTECTED] writes:
We know: Everything between the \F and the next funny character is the
format specifier. This allows extensions to the printf-specifiers:
Cool, Perlish, scary.
Examples:
[snip]
On Mon, Jun 16, 2003 at 10:15:57AM -0700, Michael Lazzaro wrote:
On Friday, June 13, 2003, at 10:26 PM, David Storrs wrote:
my $a = 'foo';
my Int $b = $a; # legal; $b is now 0; is there a warning?
my $c = $b; # is $c 0, or 'foo'?
0, I think. Or specifically, CInt
On Mon, Jun 16, 2003 at 11:37:06AM -0700, Michael Lazzaro wrote:
[...]
But there is broad support for the idea that the somewhat elderly
printf syntax is a PITA, and that printf, in general, should be
completely unnecessary since we already *have* interpolated strings,
fer pete's sake.
A
On Mon, Jun 16, 2003 at 11:47:35AM -0700, Austin Hastings wrote:
Although it occurs to me that there might be such a thing as Int
properties and Str properties, and maybe the conversion propagates
the appropriate ones.
That is:
my $a = foo but $purple ;
$a but= false;
$a but= prime;
On Mon, Jun 23, 2003 at 03:13:23PM +0100, sitaram wrote:
Hi,
I am a new one Perl.
I want a book which gives the Knowledge about perl.
I learned up to some extent using the online books.
I want a book which is tells me about functions(system,Built in) in brief.
Can U send the URL for such a
On Tue, Jun 24, 2003 at 06:14:52AM -0700, Sean O'Rourke wrote:
On Tue, 24 Jun 2003, Leopold Toetsch wrote:
[...] Nobody answered, if we need another
Sub class implementing the old invoke/ret scheme ...
I'd say no. P6C is now compiling to an obsolete architecture.
While we should all
On Tue, Jun 24, 2003 at 04:04:29PM +0100, Andrew Wilson wrote:
On Tue, Jun 24, 2003 at 07:58:32AM -0700, David Storrs wrote:
/me shows ignorance yet again.
For those of us who are not hardware types...what is the new
machine? The Itanium? Does that really have enough market
Thinking about it, I'd rather see lvalue slices become a nicer version
of Csplice().
my @start = (0..5);
my @a = @start;
@a[1..3] = qw/ a b c d e /;
print @a; # 0 a b c d e 4 5
# Similarly:
@a = @start;
my $r_slice = [EMAIL PROTECTED];
@$r_slice =
On Tue, Jul 08, 2003 at 05:52:04PM -0700, Austin Hastings wrote:
--- Jonadab the Unsightly One [EMAIL PROTECTED] wrote:
Am I now thinking clearly?
I don't think so.
If you've created two separate arrays that happen to start with related
values, then the changes to the first won't
On Fri, Jul 18, 2003 at 06:05:52PM -0400, Benjamin Goldberg wrote:
What would happen if I used 1,2,3 instead of 1..3? Would it do the same
thing?
I would think so.
I wanna know what happens if I do:
@a[0,2,4] = qw/ a b c d e /;
Yup, you're right, I didn't consider
On Mon, Jul 21, 2003 at 12:19:11PM -0700, Austin Hastings wrote:
Likewise:
my $fh = open perl.1.gz;
$fh =~ /Grammars::Languages::Runoff::Nroff(input_method
= Grammars::Languages::Runoff::tbl(input_method
= Grammars::Language::Runoff::eqn(input_method
=
On Mon, Sep 15, 2003 at 11:49:52AM -0400, Gordon Henriksen wrote:
Austin Hastings wrote:
Given that threads are present, and given the continuation based
nature of the interpreter, I assume that code blocks can be closured.
So why not allocate JITed methods on the heap and manage them as
On Fri, Oct 24, 2003 at 12:57:18AM -0600, Luke Palmer wrote:
Presuming you can do:
(who = $name, why = $reason) := (why = $because, who = me);
(from A6)
Does that imply that you can do:
sub routine (name = $nombre, date = $fecha) {...}
Anyway, I just realized that this is
On Tue, Jan 13, 2004 at 10:16:48PM -0700, Luke Palmer wrote:
sub mark_that_we_have_reached_max_records() {
$max_reached = 1;
}
if !$max_reached some_expensive_lookup_function() $MAX_RECORDS {
mark_that_we_have_reached_max_records();
return;
}
On Wed, Jan 14, 2004 at 10:59:52AM -0500, Melvin Smith wrote:
I think Perl6 will allow a hint like so:
my int $max_reached;
The important thing is that $max_reached is used simply as a conditional,
and you don't pass it to a routine or otherwise use it in a way to cause it
to be
On Wed, Jan 14, 2004 at 11:57:05AM +, Richard Nuttall wrote:
How about
$test = sub
{
if ( some_expensive_lookup_function() = $MAX_RECORDS )
mark_that_we_have_reached_max_records();
$test = sub{};
};
Then call $test() as needed;
Neat. I wouldn't
On Wed, Apr 14, 2004 at 10:06:23PM +0200, Juerd wrote:
If on your keyboard ` is in a worse place than {}, I'd like to know
where it is.
Juerd
Very top row, one space right of the F12 key. Extremely awkward.
(This is a US keyboard on a Dell Inspiron 5100 laptop.)
Please put me down as
On Thu, Apr 15, 2004 at 11:45:27AM +0200, Juerd wrote:
David Storrs skribis 2004-04-14 22:39 (-0700):
Very top row, one space right of the F12 key. Extremely awkward.
(This is a US keyboard on a Dell Inspiron 5100 laptop.)
That is inconvenient.
Yup.
1) ` looks like it should
Folks, this discussion seems to be spinning. All the points, on both
sides, have been made and are being repeated with only slight
variation. We've all made our cases--why don't we drop the issue for
a while and let Larry ruminate? I think we can all agree that he will
give the idea a fair
On Fri, Apr 16, 2004 at 05:30:01PM -0700, chromatic wrote:
Perl.com has just made A12 available:
http://www.perl.com/pub/a/2004/04/16/a12.html
Warning -- 20 pages, the first of which is a table of contents.
Enjoy,
-- c
It's here, it's here, it's he!!
*Ahem*
On Tue, Jun 08, 2004 at 01:08:13PM -, Ingo Blechschmidt wrote:
Hello,
quoting Apocalypse 6:
You may ask a subroutine to wrap itself up in another subroutine in
place, so that calls to the original are intercepted and interpreted by
the wrapper, even if access is only through the
On Sun, Jun 13, 2004 at 03:40:27AM +0200, Pedro Larroy wrote:
What advantages have to use characters not in standard keyboards? Isn't
it a little scary?
Well, what do you consider a 'standard' keyboard? The zip
operator/Yen sign probably appears on most keyboards in Japan, but on
very few in
On Thu, Jun 24, 2004 at 12:43:30PM -0700, Scott Bronson wrote:
So, in summary, though 0==false appears to work, it leads to a number
of strange boundary conditions and, therefore, bugs. It's hard for new
programmers to grasp and even old hacks are still sometimes tripped up
by it. It just
On Sun, Jun 27, 2004 at 03:16:11PM -0600, Luke Palmer wrote:
But anyway, if you still want to be old school about it, then you'll end
up not caring about the scope of your $i. Really you won't. And you'll
be happy that it was kept around for you once you decide you want to
know the value
On Tue, Jun 29, 2004 at 05:31:29PM -0600, Luke Palmer wrote:
Oh no! Someone doesn't understand continuations! How could this
happen?! :-)
You need two things to bring the state of the process back to an earlier
state: undo and continuations. People say continuations are like time
On Thu, Jul 01, 2004 at 04:14:37PM -0700, Jonathan Lang wrote:
Juerd wrote:
If you're really enamoured with the infix operator syntax, consider this
possibility:
sub infix:- ($before, $after) {
$before; # is this line redundant?
return $after;
}
print $a - $b -
On Sat, Jul 03, 2004 at 01:02:34AM -0600, Luke Palmer wrote:
But indeed there are cases where it is a problem:
my $x = 2;
sub mklist () {
return map { 2 * $_ } 0..10;
}
my @list = mklist;
say @list[0..4]; # 0 2 4 6 8
$x = 1;
say @list; #
On Tue, Jul 06, 2004 at 06:39:07PM -0600, Luke Palmer wrote:
Matija Papec writes:
Would there be a way to still use simple unquoted hash keys like in old
days ($hash{MYKEY})?
Of course there's a way to do it. This is one of those decisions that I
was against for the longest time,
On Wed, Jul 14, 2004 at 07:40:33AM +0200, Ph. Marek wrote:
To repeat Dave and myself - if
@x = 1 .. Inf;
then
rand(@x)
should be Inf, and so
print $x[rand(@x)];
should give Inf, as the infinite element of @x is Inf.
Does it even make sense to take the Infiniteth element
On Sat, Jul 17, 2004 at 06:23:50PM -0400, Austin Hastings wrote:
On Saturday, 17 July, 2004 01:53 Sat, Jul 17, 2004, Juerd wrote:
Do we have a :) operator yet?
It's an adverbial modifier on the core expression type. Does
nothing, but it acts as a line terminator when nothing but
On Sun, Jul 18, 2004 at 05:36:58PM -0700, Dave Whipp wrote:
truncate Vs append would be infered from usage (assign = truncate). One
might be able to infer read Vs write in a similar way -- open the file based
on the first access; re-open it (behind the scenes) if we write it after
reading it.
On Sun, Jul 18, 2004 at 08:39:09PM -0500, Rod Adams wrote:
Case 1:
So I wanted to do a read/write scan, so I create my TextFile, start
reading in data, so the file is opened for reading. Then, I come to the
part where I want to update something, so I do a write command. Suddenly
the file
On Mon, Jul 19, 2004 at 03:37:12PM -0500, Rod Adams wrote:
I think part of the mental jam (at least with me), is that the
read/write, exclusive, etc, are very critical to the act of opening the
file, not only an after the fact restriction on what I can do later. If
I cannot open a file for
On Wed, Jul 21, 2004 at 04:37:29PM -0700, Larry Wall wrote:
No Yes
-- ---
@foo@foo[1]
%bar%bar{a} or %bar«a»
$foo.bar$foo.bar()
foo foo(1)
In this worldview, $foo is an exception only because it doesn't naturally
have a
On Sat, Jul 24, 2004 at 02:23:10PM -0700, Brent 'Dax' Royal-Gordon wrote:
Jonadab the Unsightly One wrote:
Oh, and here's me resisting the urge to suggest that use ought to
automatically install from the CPAN anything that isn't present, as a
core behavior right out of the box.
Security
On Sat, Aug 07, 2004 at 03:55:21PM +0100, Nicholas Clark wrote:
On Sat, Jul 24, 2004 at 02:50:18PM -0700, David Storrs wrote:
#!/usr/bin/perl6
#!/usr/bin/perl
I stated perl6 explicitly to be, well, explicit.
#use warnings; # Note that I am NOT explicitly using these
#use strict
On Tue, Aug 10, 2004 at 11:07:59AM -0700, Larry Wall wrote:
2) In the absence of evidence to the contrary, methods always
assume they have *no* arguments. For methods:
2a) A method not followed by a left paren or colon has no
arguments.
Just checking--whitespace
There has been a lot of discussion in the other threads lately about
iterators. I was wondering if there will be an easy way to create a
bidirectional iterator? Toy example to show what I'm thinking:
for(1..10) {
next if /7/; # always skip 7
prev if 9 !rand 3; # occasionally
On Fri, Sep 03, 2004 at 08:09:23AM -0400, Joe Gottman wrote:
-Original Message-
From: Larry Wall [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 02, 2004 8:41 PM
To: Perl6
Subject: Re: Reverse .. operator
On Thu, Sep 02, 2004 at 08:34:22PM -0400, Joe Gottman wrote:
On Dec 15, 2004, at 5:36 PM, Abhijit Mahabal wrote:
I think that slackness-on-demand is a better policy than
strictness-on-demand, but that, again, is just my opinion
Until now, the policy in Perl has always been that it is as slack and
forgiving as possible, and you have to ask if you want
On Dec 10, 2004, at 11:05 AM, Abhijit Mahabal wrote:
Consider a class (e.g., the hypothetical Geometry::Triangle) that can
have several attributes (side1, side2, side3, angle1, ang_bisector1,
side_bisector, altitude1 and so forth), most of which will not be
needed for most instances of
On Dec 15, 2004, at 6:11 PM, Abhijit Mahabal wrote:
David Storrs wrote:
On Dec 15, 2004, at 5:36 PM, Abhijit Mahabal wrote:
I think that slackness-on-demand is a better policy than
strictness-on-demand, but that, again, is just my opinion
Until now, the policy in Perl has always been
On Sat, Jan 08, 2005 at 12:48:32PM -0800, Ashley Winters wrote:
sub canon( $subjet, $complement)
- $s = $subjet{$*Global}, $c = $complement
{
my @foo = ...;
for @foo - $bar; $remaining = @foo.elems {
# $bar contains an element, $remaining contains the number of
On Sat, Jan 08, 2005 at 11:37:06AM -0700, Craig DeForest wrote:
@a[4; 0..5];
a 1x6 array (probably correct)? Or a 6 array (probably not
correct)?
For the ignorant among us (such as myself), what is a 6 array? Google
and pdl.perl.org did not yield any immediate answers.
--Dks
--
On Thu, Jan 13, 2005 at 07:35:19PM -0500, Joe Gottman wrote:
In Perl5, given code like
for (my $n = 0; $n 10; ++$n) {.}
the control variable $n will be local to the for loop. In the equivalent
Perl6 code
loop my $n = 0; $n 10; ++$n {.}
$n will not be local to the loop but
On Fri, Jan 14, 2005 at 02:46:58PM -0500, Austin Hastings wrote:
rules, I can easily have it either way.
{for (my $n=0; $n10; ++$n) {...}} # Local to loop
for (my $n=0; $n10; ++$n) {...}# Persistent
--Dks
But there's no clean way to make some of them temporary and
Given that Perl 6 won't support an actual do-while loop a la C++ (and
yes, I know that Perl5 didn't either), how would you accomplish that?
That is, I'd like to have a loop that runs once, then checks its
condition to see if it should repeat and continues to repeat as long
as the condition is
On Thu, Feb 10, 2005 at 09:45:59AM -0800, Larry Wall wrote:
That's spelled
loop {
$foo = readline;
...do stuff with $foo...
} while ( $foo );
these days.
Larry
Cool, perfect. Thanks.
--Dks
--
[EMAIL PROTECTED]
On Fri, Feb 11, 2005 at 05:33:29PM -0800, Ashley Winters wrote:
On Thu, 10 Feb 2005 08:59:04 -0800, David Storrs [EMAIL PROTECTED] wrote:
On Wed, Feb 09, 2005 at 05:13:56AM -0600, Rod Adams wrote:
($k, $v) == pop %hash;
make sense to anyone except me?
... the only time it's useful
On Sat, Feb 12, 2005 at 06:39:01PM +1100, Damian Conway wrote:
pick - select at random from a list, array, or hash
OOC, will there be a way to control where Cpick gets its randomness
from? (e.g. perl's builtin PRNG, /dev/random, egd, etc)
--Dks
--
[EMAIL PROTECTED]
On Tue, Feb 15, 2005 at 11:06:51AM -0800, Larry Wall wrote:
But what y'all are talking about above is the other end--the return
type. And maybe we need to enforce a newbie-friendly invariant on that
end as well. I suppose we could default to not accepting junctional
return values by
On Thu, Mar 03, 2005 at 04:09:26PM -0800, Larry Wall wrote:
On Thu, Mar 03, 2005 at 12:36:00PM -0800, Brian Ingerson wrote:
: Thanks for the mind expanding reply.
You're welcome. Next time don't eat blue sugar cubes from my frig. :-)
I know what you're thinking. 'Why, oh why, didn't I
On Sun, Mar 06, 2005 at 11:58:43PM -0800, Larry Wall wrote:
On Sun, Mar 06, 2005 at 02:13:09AM -0700, Luke Palmer wrote:
: What is output:
:
: sub foo($x, ?$y, [EMAIL PROTECTED]) {
: say x = $x; y = $y; z = @z[];
: }
:
: my @a = (1,2,3);
: foo($x, @a);
I think
On Sun, Mar 06, 2005 at 04:57:38PM +0100, Leopold Toetsch wrote:
On behalf of the Parrot team I'm proud to announce the release of
Parrot 0.1.2.
First: Congratulations to everyone for this release!
Second: What will it take before Parrot moves to a 0.2 (0.3, 0.4...)
release?
--Dks
On Mon, Mar 07, 2005 at 03:43:19PM +0100, Aldo Calpini wrote:
don't know if it helps, but I guess that you can also write it like
this, if you prefer:
sub greeting(Str $person) {
returns Str;
is export;
Hello, $person;
}
(this guess is based on
On Mon, Mar 07, 2005 at 05:36:08PM +0100, Aldo Calpini wrote:
David Storrs wrote:
Urk. I, for one, will definitely find this surprising. I would have
expected:
x = whatever; $y = 1; z = 2 3
to obtain what you have expected, you need to explicitly treat the array
as a list of values
On Mon, Mar 07, 2005 at 04:58:29PM -0800, Larry Wall wrote:
In fact, we really haven't specified what happens when you say
my Int @a is shape(3) := [1,2];
my Int @b is shape(3) := [1,2,3,4];
[...]
But I also have this nagging feeling that the user wouldn't have
specified
On Mon, Mar 07, 2005 at 05:15:14PM -0800, Larry Wall wrote:
On Mon, Mar 07, 2005 at 02:20:47PM -0800, David Storrs wrote:
: Yes, I know. That's what I meant by ...arrays are objects...(sort
No, they're real objects. (Though it's .elems rather than .length, since
we've banished the l word
On Mon, Mar 07, 2005 at 07:50:47PM -0800, Larry Wall wrote:
On Mon, Mar 07, 2005 at 05:37:53PM -0800, David Storrs wrote:
: On Mon, Mar 07, 2005 at 04:58:29PM -0800, Larry Wall wrote:
: Is
: there is then any way to explicitly leave off an element. Can I do
: this:
:
: sub foo( Int
Is there a way to find the name of ?SUB ? It would be useful for
error-logging and -reporting.
--Dks
On Tue, Mar 08, 2005 at 10:29:30PM -0800, Darren Duncan wrote:
[...]
By using subtypes in this way, I could remove a lot of explicit input
checking code from my methods, which is great. Also, the where
clause is not being repeated for every argument or attribute or
variable declaration.
On Wed, Mar 09, 2005 at 03:38:52PM -0600, Rod Adams wrote:
There lingers the case of:
use Foo; # from above, exports bar is MMD::Random
multi sub bar {...}
Does this generate an error, since one could expect this particular bar
to be Manhattan? Or does it assume Random, since
At 17:53 +0100 3/10/05, Thomas Sandlaß wrote:
[request for clarification of 'covariant' and 'contravariant' usage]
'Co' means together like in coproduction. And 'contra' is the opposite
as in counterproductive. With instanciating parametric types the question
arises how a subtype relation
On Thu, Mar 10, 2005 at 02:22:20PM -0600, Rod Adams wrote:
David Storrs wrote:
On Wed, Mar 09, 2005 at 03:38:52PM -0600, Rod Adams wrote:
use Foo; # from above, exports bar is MMD::Random
multi sub bar {...}
Does this generate an error, since one could expect this particular bar
On Sat, Mar 12, 2005 at 09:36:24PM +0100, Juerd wrote:
Larry Wall skribis 2005-03-12 12:26 (-0800):
And arguably, the current structure of join is that the delimiter is
the invocant, so cat should be defined as
''.join(@foo)
This is what Python does. It does not make any sense to
On Tue, Mar 15, 2005 at 08:23:19AM -0800, Larry Wall wrote:
On Tue, Mar 15, 2005 at 10:51:57AM +0100, Juerd wrote:
: Autrijus suggested indeed or id, of which I like indeed better,
: because I'd like to continue using id with databases.
id is too heavily overloaded with identifiers and
On Wed, Mar 16, 2005 at 12:00:28PM -0500, Aaron Sherman wrote:
The one obvious thing to POD users is the replacement of with [] or
{}. Why is this? Because and are used in un-balanced ways in a large
number of situations, so they should not be the primary bracketing
constructs.
On Wed, Mar 16, 2005 at 01:30:04PM -0500, Aaron Sherman wrote:
On Wed, 2005-03-16 at 12:25, David Storrs wrote:
I quite like as the bracketing characters. They are
visually distinctive, they connect well with their adjacent C/X/L/etc
without visually merging into it (compare Lfoo with L
On Thu, Mar 17, 2005 at 05:04:53PM -0500, Aaron Sherman wrote:
On Thu, 2005-03-17 at 12:28, Brian Ingerson wrote:
The interesting thing to me is that all 3 syntaxes map over the same
data model and thus are easily interchangable.
It is, however, contrary to the spirit of POD for you or
On Sat, Mar 26, 2005 at 10:13:54AM -0800, Larry Wall wrote:
The thing is that these MAD props are hung on whatever node is handy
at the time, [...]. That's the main reason for the first pass of
translator, to reattach the madprops at a more appropriate place in
the tree.
[...]
But with
On Fri, Apr 08, 2005 at 05:03:11PM +0300, wolverian wrote:
Hi wolverian,
one day a friend asked if Perl 5 had a REPL facility.
(Read-Eval-Print-Loop). I told him it has perl -de0, which is different
[...]
In Perl 6, the generic solution to fix this (if one wants to fix it)
seems, to me, to
1 - 100 of 128 matches
Mail list logo
