Larry Wall wrote:
On Thu, Mar 11, 2004 at 01:18:52PM -0800, chromatic wrote:
: On Thu, 2004-03-11 at 13:04, Larry Wall wrote:
:
: Well, okay, not a boolean. More like a troolean.
:
: Unless it's a falselean.
It's more truelean than falselean by a 2/3rds majority. And it's
much more if you
Robin Berjon wrote:
Specifying the OS is not enough, you need at least the keyboard layout.
It would be impossible to have shortcuts involving | or \ on a French
keyboard since they are respectively Alt-Shift-L and Alt-Shift-:
OS X / iBook / fr-fr
« Alt-è
» Alt-Shit-è
Good point. I tend to
Mark J. Reed wrote:
On 2004-04-13 at 13:16:02, David Cantrell wrote:
Perl 6, we are promised, will try to run legacy code unchanged. How
will it spot such legacy code?
My understanding has been that perl6 will assume a program is Perl 5 unless
it sees a Perl 6 keyword such as 'module' or
Thomas A. Boyer wrote:
Matthew Walton wrote:
That could be problematic, because if Perl 6 sees something like:
my %myhash;
%myhash{'foo'} = 'bar';
Is it going to think 'ahah, perl 6' or 'perl 5 with errors'?
It's going to think 'ahah', perl 5'. Because it doesn't contain any Perl
6 keyword
Thomas A. Boyer wrote:
The original question was how do I label my code as Perl 5? The
correct answer, according to Apocalypse 1, is to start your source with
package. If you didn't want to put your code in a package, then start
it with package main.
The other question was how do I label my
Juerd wrote:
chromatic skribis 2004-04-14 12:32 (-0700):
That's exactly my objection to this idea. I think it goes too far to
make simple things simpler while making complex things impossible.
Absolutely false.
This is an addition to the already existing {}, which should stay.
%foo{
Juerd wrote:
Sean O'Rourke skribis 2004-04-15 8:55 (-0700):
I find that there are still plenty of contexts in which `` is nice and
security is irrelevant.
This is the second time in this thread that I read about security being
unimportant. I still don't know what to say about it, though I feel
I know these were discussed to death not that long ago, but reading
Apocalypse 12 I had a query I couldn't remember if it had been covered
before or not, and I certainly don't recall seeing it in the Apocalypse,
although I've not read the entire thing with as much attention as I
might like yet
Luke Palmer wrote:
Matthew Walton writes:
But can I do
@things».=method();
Of course.
Excellent. Thankyou.
Not this time :-)
Next time then, probably.
Mark J. Reed wrote:
Let me just chime in with my support for John's basic idea. I would
definitely prefer that it be easy to arrange things such that
$obj.foo = 'bar'
winds up invoking a method on $obj with 'bar' as an argument, rather
than invoking a method on $obj that returns an lvalue to
Stéphane Payrard wrote:
Le Wed, May 12, 2004 at 02:00:42AM +0200, le valeureux mongueur Pedro Larroy a dit:
Hi
Is there any chance that in perl6 there will be the possibility to write
if/else statements without {}s with the condition at the beginning?
Like
if (condition)
statement;
In
Larry Wall wrote:
On Wed, May 12, 2004 at 09:47:04AM +0100, Matthew Walton wrote:
: For some reason, lots of people don't like it when indentation is
: what's controlling their code structure...
Indentation is a wonderful form of commentary from programmer to
programmer, but its symbology
Larry Wall wrote:
On Wed, May 12, 2004 at 11:37:44PM +0200, Juerd wrote:
: Aaron Sherman skribis 2004-05-12 17:30 (-0400):
: I like C... I like it a LOT. In fact, I'm partial to the idea that
: it should be usable anywhere
:
: I agree. It'd make even more of my pseudo code (#perlhelp and
:
I actually find myself having somewhat coherent thoughts on this matter.
Apologies if they seem rather obvious or naive, but I'm still new to all
this.
Dov Wasserman wrote:
my $id = ...;
my Int age = ...;
my Str $name = ...;
my DbHandle $db = ...;
my Int of Hash @array = ...;
Therefore, the
Austin Hastings wrote:
I think of this as very much like the typed-undef we discussed last
month or so: ... should return an unthrown exception wrapped in
undef-ness.
The type returned by ... should just have a multitude of type-casting
tricks associated:
my int $i = ...; # Fails at compile
[EMAIL PROTECTED] wrote:
Austin Hastings wrote:
my int $i = ...; # Fails at compile time -- no good conversion.
my Int $i = ...; # Warns at compile time, fails at runtime.
I don't get the reasoning here. If Yada Yada Yada is to indicate code
that you haven't written yet, it should never
Mark Lentczner wrote:
All -
Awhile back, I saw Larry Wall give a short talk about the current design
of Perl 6. At some point he put up a list of all the operators - well
over a hundred of them! I had a sudden inspiration, but it took a few
months to get around to drawing it...
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 reference:
$id = $subref.wrap({
#
Austin Hastings wrote:
Perhaps we could consider the junctive lvalues as a sort of implied
?= operation:
junction(@list) = value
means
unless junction(@list) == value
{
given junction {
when 'none' { (@list.grep value) = undef; }
when 'any' { for 0 .. random(@list) {
Mark J. Reed wrote:
On 2004-06-14 at 22:58:58, Matthew Walton wrote:
'it would be better to explicitly just say
(@list.grep value) = undef
although I think that might be supposed to be
(@list.grep value) »= undef;
Those do different things according to my understanding. The first
removes all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michele Dondi wrote:
| I don't know if this is already provided by current specifications, but
| since I know of Perl6 that is will support quite a powerful system of
| function prototyping (signatures?), I wonder wether it will be possible
| to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Hodges wrote:
| --- Luke Palmer [EMAIL PROTECTED] wrote:
|
|Paul Hodges writes:
|
|So, in P6:
|
| if 0 { print 0\n; } # I assume this won't print.
| if '0' { print '0'\n; } # I assume this won't print.
| if ''{ print ''\n;}
Larry Wall wrote:
The rand function may be a bad example, since it's by nature a
generator, and you should maybe have to work harder to get a single
value out of it. We haven't really said what $fh xx 100 should do,
for instance. I guess the real question is whether xx supplies a
list context to
Joe Gottman wrote:
There's something wrong with the mailing list archives at
http://dev.perl.org/perl6/lists/. I can get to this page OK, but when I
click on a link to the perl6-internals or perl6-language archives, I get a
This page cannot be displayed error.
The perl.org list server's been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Aug 2004, at 18:04, Luke Palmer wrote:
The one in Perl 5 that stands out most was the cause for the only patch
I ever sent to p5p: the rand function. rand $x will give you a
uniformly distributed random number in [0, $x) for any $x EXCEPT 0. If
Larry Wall wrote:
On Fri, Aug 20, 2004 at 09:21:02AM +0100, Matthew Walton wrote:
: It would be nice if rand behaved a bit more sanely in Perl 6. I can
: understand the reasoning for making rand 0 produce between 0 and 1, but
: that doesn't mean I have to like it.
What makes you think
Aaron Sherman wrote:
=table C$_ | C$x | Type of Match Implied | Matching Code
=row Any | CodeC $ | scalar sub truth | match if
C$x($_)
That's (the above comments aside) the same thing, and as I said when
Luke suggested it, it seems fine if that's the way we'd prefer to go.
Aaron Sherman wrote:
I was thinking about the case where you use a module, only to define a
class that you then instantiate like this:
use Some::Module::That::Defines::A::Class;
our Some::Module::That::Defines::A::Class $foo := new;
and I keep thinking that that's too redundant.
Alexey Trofimenko wrote:
On Fri, 20 Aug 2004 09:21:02 +0100, Matthew Walton
[EMAIL PROTECTED] wrote:
On 19 Aug 2004, at 18:04, Luke Palmer wrote:
[...]
my $num = $param == 0 ?? 0 : rand $param;
my $num = $param == 0 ?? 0 :: rand $param;
surely?
a little off theme.. I wanna ask, could
Michele Dondi wrote:
On Thu, 2 Sep 2004, Larry Wall wrote:
To declare a multidimensional array, you add a shape parameter:
my num @nums is shape(3); # one dimension, @nums[0..2]
my int @ints is shape(4;2); # two dimensions, @ints[0..3; 0..1]
Just a random thought, and probably a minor
Andrew Rodland wrote:
On Tuesday 21 September 2004 07:18 pm, Thomas A. Boyer wrote:
Larry Wall wrote:
Somebody needs to talk me out of using A..Z for the simple cases.
Larry
[ for array dimension placeholder ]
That might confuse users of languages that were not
C-syntax-influenced, who think
Austin Hastings wrote:
Michele Dondi wrote:
On Sun, 17 Oct 2004, Matt Fowles wrote:
Google groups has nothing for Perl6.language between October 2 and 14.
Is this really the case? (I had not signed up until shortly before
Yes: no traffic at all for quite a while...
Does this mean that we're
Larry Wall wrote:
On Tue, Oct 19, 2004 at 09:35:27PM +0100, Matthew Walton wrote:
: Austin Hastings wrote:
: Does this mean that we're done? :)
:
: No, it means Larry's about to stun us with something seemingly bizarre
: and inexplicable which turns out to be a stroke of genius.
The only
I suggest you read more about Parrot... it's designed to allow these
things. There is a project (Ponie) to make Perl 5 run on Parrot, and
there will be other languages as well - which will be able to call each
others libraries. Making the Perl 5 libraries available to Perl 6 being
a primary
This is just to clarify something from S13.
If I declare, for example
multi sub *infix:+ (EvilNumber $lhs, EvilNumber $rhs) { ... }
Then if I run
my EvilNumber $a;
my EvilNumber $b;
my EvilNumber $c = $a + $b;
I get my code, but
$a += $b;
Will attempt the default behaviour for +=, which is liable
Luke Palmer wrote:
Also, would things blow up if I specified the return types for operator
overloads, such as
multi sub *infix:+ (EvilNumber $lhs, EvilNumber $rhs) returns
EvilNumber is deep { ... }
In that case I don't see why it would blow up. If you said, say:
multi sub *infix:*
Randal L. Schwartz wrote:
Luke == Luke Palmer [EMAIL PROTECTED] writes:
Luke But you don't really need to parse to syntax highlight, either. You
Luke just need to tokenize.
Unfortunately, to tokenize, you also have to know the state of the parse.
As long as / is both divide and begin regex,
Randal L. Schwartz wrote:
Matthew == Matthew Walton [EMAIL PROTECTED] writes:
Matthew So you're saying that in Perl 6 it will be entirely impossible to
Matthew determine if / appears as the division operator or as the beginning of
Matthew a regex from a purely syntactic examination of the source
Randal L. Schwartz wrote:
Matthew == Matthew Walton [EMAIL PROTECTED] writes:
Matthew Perl 6 has formal parameters for subs, methods etc. I don't see any
Matthew mention of Perl 5-style prototypes in S6, and I honestly can't see how
Matthew they could possibly fit with formal parameters
James Mastros wrote:
Larry Wall wrote:
On Fri, Nov 26, 2004 at 07:32:58AM +0300, Alexey Trofimenko wrote:
: ah, I forget, how could I do qx'echo $VAR' in Perl6? something like
: qx:noparse 'echo $VAR' ?
I think we need two more adverbs that add the special features of qx
and qw,
so that you
Larry Wall wrote:
I rather like it too. I'm glad someone else is thinking along the
same lines. The basic problem with «...» is that most of its uses
were turning out to be more useful that the corresponding
In fact, I was thinking about all this on the way home from Seattle
yesterday (a
Larry Wall wrote:
I thought so.
: I don't think I've ever used a hash slice in my life. Is there something
: wrong with me?
No, a lot of people are naturally monoindexous.
I like that word.
: * The :w splitting happens after interpolation. So
:
: « foo $bar @baz »
:
: can end up
Juerd wrote:
Matthew Walton skribis 2004-12-01 9:55 (+):
Yes, that would be fun... almost worth throwing out a compiler warning
for that, especially if we've still got use warnings. Something like
Warning: «{ }» creates empty list
It should generate a warning similar to the warning
Larry Wall wrote:
: of course, that analogy isn't going to work for true functions, which
: returns the same all the time, for some given set of arguments.
Oh, well, we pissed off the mathematicians long ago. :-)
At least we had the sense to call them subroutines instead of functions.
Of
Luke Palmer wrote:
The remaining problem is what to do about unary dot. Repeated here for
the, er, benefit? of p6l:
class Duple {
has $.left;
has $.right;
method perform (oper) {
oper($.left);
oper($.right);
}
}
Let's change that
Elyse M. Grasso wrote:
But you need to process the file while you haven't reached the end yet, or
until you reach the end. And I can't think of an occasion where I knew going
in what the length of the file I was processing was going to be. I suppose
foreach might make sense if you sucked in the
Austin Hastings wrote:
I'll guess that you're pointing at
.:send_one($_);
Which supposedly uses topic to resolve .:send_one into $this.send_one.
If that works, then I'm happy -- I like being able to control topic and
$_ differently. But if Cfor changes topic, then what?
OUTER::.:send_one($_);
Larry Wall wrote:
On Sun, Dec 05, 2004 at 12:05:46AM +, Matthew Walton wrote:
: I'm sorry, but from a C++ background, overriding postcircumfix:( )
: feels far more natural to me than setting 'is default' on some method.
That only works for disambiguation if you know which .() to call
Michele Dondi wrote:
On Sun, 5 Dec 2004, Matthew Walton wrote:
At least we had the sense to call them subroutines instead of functions.
Of course, that also upset the mathematicians, who wanted to call them
functions anyway. Go figure.
That might be because the mathematicians haven't heard
Austin Hastings wrote:
David Storrs wrote:
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
Juerd wrote:
This probably goes against everything a shell based platform wants, but
would it be possible to give the program a sub-like signature?
I ask this after another painful session of forgetting how things
work, reading Getopt::Long's documentation.
signature (
Rule $pattern,
Michele Dondi wrote:
On Tue, 8 Feb 2005, Matt Fowles wrote:
pipe dreams
Juerd wondered if he could mix = and == in a sane way. The answer
appears to be no. Once you bring in == you should stick with it.
Huh?!? It doesn't seem to me that the answer is 'no'. In fact C ==
is supposed to be
Rod Adams wrote:
Does
($k, $v) == pop %hash;
or
($k, $v) == %hash.pop;
make sense to anyone except me?
Makes sense to me. Although I would be more inclined to think of pop as
returning a pair - but does a pair in list context turn into a list of
key, value? If so then the above makes lots of
Matt Fowles wrote:
All~
On Tue, 08 Feb 2005 17:51:24 +0100, Miroslav Silovic [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Well, we see the same kind of thing with standard interval arithmetic:
(-1, 1) * (-1, 1) = (-1, 1)
(-1, 1) ** 2 = [0, 1)
The reason that junctions behave this way is
Matt Fowles wrote:
This is Just Wrong, IMO. How confusing is it going to be to find that
calling is_prime($x) modifies the value of $x despite it being a very
simple test operation which appears to have no side effects?
As far as I can see it, in the example, it's perfectly logical for
delurk
even sillier question:
if [a.z] matches a, . and z
and [a...] matches all characters from a including (for some
definition of 'all')
how will be range \x21 .. \x2e written?
[!..\.]? (i.e. . escaped?)
/delurk
I was assuming from Larry's mail that [a...] would parse as either:
On Thu, Apr 21, 2005 at 11:45:27AM +0200, Paul Johnson wrote:
It certainly makes more sense to me that the answer would be 2 2. But
however it ends up, so long as we know what the answer will be, we can
utilize it effectively in our programs.
The trick with this construct usually in C is
.
On 15 May 2005, at 16:17, Rob Kinyon wrote:
Right now, P6 has $?SELF and I'm saying that instead of using $?SELF,
we should use $self wherever $?SELF would be used. $_ is still the
topic and would be the default invocant if you have .method($foo).
What I'm saying is that you can have
method (
On 15/05/05 22:48 +0100, Matthew Walton wrote:
I don't think that is what Rob is saying at all.
It wasn't aimed entirely at Rob. I have a bad habit on mailing lists of
vaguely replying to the entire thread without remembering who said what
and being too lazy to check.
My read:
.method
Springing out of the ashes (and a job where I have to write Java) for my
first post in years:
On Fri, 04 Jan 2008 13:13:11 -0800, Dave Whipp [EMAIL PROTECTED] wrote:
I agree that adding a parallel forall (and similar statements) via a
pragma will be easy if the appropriate underlying machinery
On Fri, 2008-01-11 at 10:34 -0800, Dave Whipp wrote:
Matthew Walton wrote:
I wouldn't agree with that at all. I think of arrays as ordered constructs,
so I'd want the default iteration over my array to happen in the order of
the indices.
I guess that depends on whether you think
On Sat, Jun 13, 2009 at 1:08 AM, Larry Wallla...@wall.org wrote:
Nevertheless, for any major methods borrowed from Perl 6, I'm not
inclined to change them that drastically. Much more likely to
define them as sugar for the more general list operators:
.push means .=append
Complex or not in that sense, it complicates things in allowing the value to
be changed by another path. I think that is something we want to avoid
doing, not present as a feature. Much of my original post concerns the
actual meaning, not whether it is considered simple.
Since then, I see
Complex or not in that sense, it complicates things in allowing the value to
be changed by another path. I think that is something we want to avoid
doing, not present as a feature. Much of my original post concerns the
actual meaning, not whether it is considered simple.
Since then, I see
As I understand it, in Perl 6 a method of a class, as indeed all
similar things like a sub or a regex, is represented by an object. If
it's an object, I should be able to mix a role into it, right?
Something like:
role Fancy {
has $.something is rw;
}
sub a { }
a does Fancy;
a.something =
Then you could be like TeX and have releases numbered with
ever-increasing parts of an irrational number.
On Mon, Aug 10, 2009 at 12:37 PM, Mark J. Reedmarkjr...@gmail.com wrote:
Wrong reply button...
-- Forwarded message --
From: Mark J. Reed markjr...@gmail.com
Date: Mon,
Woops - forgot to reply all (I'm on an irritating mixture of lists
which set reply-to and don't, and I never remember which is which).
Sorry!
-- Forwarded message --
From: Matthew Walton matt...@matthew-walton.co.uk
Date: Tue, Aug 11, 2009 at 7:10 AM
Subject: Re: More flexible
On Thu, Sep 17, 2009 at 4:41 AM, yary not@gmail.com wrote:
Perl is being actively developed for the Parrot VM. LLVM is another
interesting option and if someone or some group would like to take it
on, it would be a welcome alternate implementation.
What parts in particular of Cobra and
On Thu, Sep 17, 2009 at 4:13 AM, Saravanan T mail2sarava...@gmail.com wrote:
Thanks everyone for sharing the links...
Thought of working in porting Data::Dumper functionality in perl 6 .Seems
like already there is .perl function which does the same..
and a monker mberends said there is a bug
On Thu, Sep 17, 2009 at 6:58 PM, yary not@gmail.com wrote:
Matthew Walton wrote
Yes, Perl 6 does - it is not backwards compatible with Perl 5.
That so? I thought Perl6 was supposed to recognize and execute perl5
code. That statement itself implies that perl6 and perl5 are different
On Thu, Oct 15, 2009 at 10:07 AM, Ovid
publiustemp-perl6langua...@yahoo.com wrote:
Reading the paper I linked to could help to clarify the issue. In short,
there are times under my current understanding of roles where you *can't*
resolve the conflicts. Two roles, each providing and
On Tue, Oct 20, 2009 at 2:32 PM, Mark J. Reed markjr...@gmail.com wrote:
On Mon, Oct 19, 2009 at 11:47 PM, Jon Lang datawea...@gmail.com wrote:
Because a method is part of a role, and ought to abide by the same
terms by which the role abides. If Logging doesn't do Numeric, it
shouldn't have
On Tue, Oct 20, 2009 at 5:35 PM, David Green david.gr...@telus.net wrote:
I would expect $foo where {$_ ~~ X} and X $foo simply to be different
ways of writing the same thing, but whatever works!
Yes, but the where clause lets you test against multiple types at
once. They don't participate in
On Thu, Nov 12, 2009 at 2:30 PM, Richard Hainsworth
rich...@rusrating.ru wrote:
Can't exec svn: No such file or directory at build/gen_parrot.pl line 47.
You need to install Subversion in order to allow the build script to
obtain Parrot.
On Wed, Jan 27, 2010 at 1:19 PM, Carl Mäsak cma...@gmail.com wrote:
Mark (), Carl ():
S05 describes tr/// in terms of the .trans function, a handsome but
very different beast. Specifically, it doesn't seem to have a scalar
context, with which one could count things.
What does trans return in
I think the closest things we've got to pattern matching come from a
combination of multiple dispatch, where clauses and signature
unpacking. I don't know much about the latter, but a where clause can
discriminate multiple dispatch variants based on parameter values
rather than just the type, so
Rakudo in its normal operation will compile the program, then run it
immediately. You can, however, get it to save the compiled code for
later use i fyou wish.
On Sun, Mar 14, 2010 at 4:09 PM, dell wendell_hatc...@comcast.net wrote:
Hello,
I had just began looking at the perl6
On Mon, Apr 12, 2010 at 1:22 PM, Shawn H Corey shawnhco...@gmail.com wrote:
Darren Duncan wrote:
See http://perlcabal.org/syn/S02.html#Names for your answers.
Thanks for the link but nowhere in it does it state tha Perl 6 names are
case sensitive. The best the do is this, which implies it
On Mon, Apr 12, 2010 at 8:04 PM, Shawn H Corey shawnhco...@gmail.com wrote:
Matthew Walton wrote:
On Mon, Apr 12, 2010 at 1:22 PM, Shawn H Corey shawnhco...@gmail.com
wrote:
So, I'll ask again: Where in the official documentation does it state
that
Perl 6 names are case sensitive?
I
Damian, I use threads in C++ a lot in my day to day job. We use an
in-house library which isn't much more than a thread class which you
inherit from and give a Run method to, and a load of locks of various
(sometimes ill-defined) kinds.
Let me say: it's not good. Threads with semaphores and
On 8 July 2011 12:28, Rajeev Prasad rp.ne...@yahoo.com wrote:
will apps made for one distribution of Rakudo work with another?
Yes, provided that the versions of Rakudo used are sufficiently
compatible (one might have newer features that you used that another
one hasn't updated to include yet,
81 matches
Mail list logo
