Larry Wall wrote:
You've more or less described the semantics available at the "use
bytes" level, which basically comes down to a pure OO approach where
the user has to be aware of all the types (to the extent that OO
doesn't hide that). It's one approach to polymorphism, but I think
it shortchang
As shown below, END blocks in Pugs are behaving differently to p5;
i.e. the Pugs END block is not being executed after die is called.
I expect this is known and a TODO but I thought I'd better report it
just in case.
# cat f.p6
print "one\n";
die "dying";
print "two\n";
END { print "in end block
On Sat, Mar 19, 2005 at 05:07:49PM -0600, Rod Adams wrote:
: I propose that we make a few decisions about strings in Perl. I've read
: all the synopses, several list threads on the topic, and a few web
: guides to Unicode. I've also thought a lot about how to cleanly define
: all the string related
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sat, 19 Mar 2005 17:19:49 +0100
. . .
2) these methods can be called in various ways:
Px = cos Py # opcode syntax
cos Px, Py # same
Px = "cos"(Py) # function call
It's been pointed out to me that A12 mentions:
Coercions to other classes can also be defined:
multi sub *coerce:as (Us $us, Them ::to) { to.transmogrify($us) }
Such coercions allow both explicit conversion:
$them = $us as Them;
as well as implicit conversions:
my Them $them = $us;
I read
I propose that we make a few decisions about strings in Perl. I've read
all the synopses, several list threads on the topic, and a few web
guides to Unicode. I've also thought a lot about how to cleanly define
all the string related functions that we expect Perl to have in the face
of all this expa
On 2005-03-19, Andy Lester <[EMAIL PROTECTED]> wrote:
>
> login: { # block to define
> how to log in
>url m|https?://james.bond.edu.au/.*| or die "there is nothing to
> log in here"
> and fill uid $username
Thanks, applied.
/Autrijus/
pgpL4svnAYVcs.pgp
Description: PGP signature
# New Ticket Created by Nick Glencross
# Please include the string: [perl #34501]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34501 >
---
osname= linux
osvers= 2.6.8-gentoo-r3
arch= i686-linux
cc= gcc 3.3.4 200406
Sat Mar 19 16:23:21 EST 2005 Mark Stosberg <[EMAIL PROTECTED]>
* typo fix
New patches:
[typo fix
Mark Stosberg <[EMAIL PROTECTED]>**20050319212321]
<
> {
hunk ./ext/Pugs-Documentation/perlkwidspec.kwid 272
be ample room for people to make out-of-band hacks for specific output
formats.
-On
Some interesting ideas here...
Date: Sun, 20 Mar 2005 07:11:11 +1000
From: Robert Barta <[EMAIL PROTECTED]>
To: libwww@perl.org
Hi all,
I have put WWW::Agent onto CPAN.
http://search.cpan.org/~drrho/WWW-Agent/
We will use it here to base on it functionality given in
WWW::Mechanize, WWW::Ro
-->
Yet Another Perl Conference, North America, 2005 Registration now
open.
Conference dates: Monday - Wednesday 27 - 29 June 2005
Location: 89 Chestnut Street http://89chestnut.com/
University of Toronto
Toronto, Ontario, Canada
On Fri, Mar 18, 2005 at 09:36:49PM -0500, Chip Salzenberg wrote:
: Nobody on #perl6 today could answer this one. Is:
: Str | Int where { $_ }
: the same as:
: (Str | Int) where { $_ }
: or:
: Str | (Int where { $_ })
: ?
"where" binds looser than |, but it's a member of a select group
On Sat, Mar 19, 2005 at 11:03:40PM +1100, Andrew Savige wrote:
: --- Autrijus Tang wrote:
: > On Fri, Mar 18, 2005 at 09:35:59PM +1100, Andrew Savige wrote:
: > > What is the best way in Perl6/Pugs to slurp a file?
: >
: > You use the slurp() primitive, implemented as r875. :)
:
: Thanks. I teste
On Fri, Mar 18, 2005 at 04:06:21PM -0700, Luke Palmer wrote:
: Larry Wall writes:
: > %::{'&infix:'}, I suspect.
:
: I suspect that's a bad idea. What about &infix:{'<'}?
Well, one could go with &infix:«<» in that case, but yes, one could
always construct an operator that violates all the standa
1) builtin methods are living in a class namespace e.g.
Float."cos"
ParrotIO."open" # unimplemented
2) these methods can be called in various ways:
Px = cos Py # opcode syntax
cos Px, Py # same
Px = "cos"(Py) # function call
Px = Py."cos
--- Autrijus Tang wrote:
> On Fri, Mar 18, 2005 at 09:35:59PM +1100, Andrew Savige wrote:
> > What is the best way in Perl6/Pugs to slurp a file?
>
> You use the slurp() primitive, implemented as r875. :)
Thanks. I tested these two forms and it's truly lovely:
my $x = slurp($fname) err die("slur
On Thu, Mar 17, 2005 at 03:59:43PM -0800, Michael G Schwern wrote:
: What it doesn't solve is the $.method vs .method issue. They look
similar
: but one works on the invocant and one works on $_. Still a trap.
Yes, and that's probably the killer of the "oc" idea. So much for
Sleep Brain, heh,
Chip Salzenberg writes:
> Nobody on #perl6 today could answer this one. Is:
> Str | Int where { $_ }
> the same as:
> (Str | Int) where { $_ }
I think it's this one. The junctive operators naturally feel pretty
tight precedence, and named operators feel loose.
> or:
> Str | (Int wh
Nobody on #perl6 today could answer this one. Is:
Str | Int where { $_ }
the same as:
(Str | Int) where { $_ }
or:
Str | (Int where { $_ })
?
Followup questions, Mr. President:
What kind of operators are "where", "of", "is", and "will"?
Is there a reason that S03 doesn't list them?
W
Larry Wall kirjoitti:
On Thu, Mar 17, 2005 at 03:59:43PM -0800, Michael G Schwern wrote:
: What it doesn't solve is the $.method vs .method issue. They look similar
: but one works on the invocant and one works on $_. Still a trap.
Yes, and that's probably the killer of the "oc" idea. So much fo
21 matches
Mail list logo
