--- On Thu, 7/9/09, Moritz Lenz mor...@faui2k3.org wrote:
. . .
Somehow the current file test syntax, 'filename' ~~ :e, looks like a not
well-though-out translation of Perl 5's syntax, -e 'filename'.
Apart from totally feeling wrong to me,
Dunno about totally. I'm still trying to get a P6
--- On Tue, 3/24/09, jason switzer jswit...@gmail.com wrote:
Basically, the perl community has largely adopted TIMTOWTDI
So how about a Tim the Toady? :)
===
Hodges' Rule of Thumb: Don't expect reasonable behavior from anything with
--- On Tue, 3/24/09, John Macdonald j...@perlwolf.com wrote:
The graphene logo inspires me to suggest that a carbon
ring be used as the logo for Parrot...
A carbon ring also has the advantages that it's regognizable as a very small
logo, even as just a favicon.ico, and can be reasonably if
(full quote below)
As Duncan said, the real question is what’s the point of having
Bit when we also have both Int and Blob. I think none.
I can't find anything in the existing synopses about Blobs.
Probably looking in the wrong place, sorry.
Blobs can handle arbitrary numbers of bits?
If so,
It seems that the following should address the issue while providing enough
indication about what is occurring:
my $bill = try { ack() } // thpp();
That seems to be closer to what the original post was desiring.
Paul
to ensure that $@ still contains what we expect at the end of each exception
handling block.
Cheerio,
Paul
--
Paul Fenwick [EMAIL PROTECTED] | http://perltraining.com.au/
Director of Training | Ph: +61 3 9354 6001
Perl Training Australia| Fax: +61 3 9354
,
Paul
--
Paul Fenwick [EMAIL PROTECTED] | http://perltraining.com.au/
Director of Training | Ph: +61 3 9354 6001
Perl Training Australia| Fax: +61 3 9354 2681
exception-related plans to p6l as they happen. ;)
All the best,
Paul
[1] Klingon semantics: It is better to die() in the attempt than to return()
in failure. I'll buy a beverage for whomever can help me translate that
back into Klingon in time for OSCON. ;)
--
Paul Fenwick [EMAIL
the hierarchy for p5 autodie?
* Is this an appropriate question for p6l? While it relates to a p5 pragma,
I hope to make the behaviour as compatible with p6 as possible.
Many thanks,
Paul
--
Paul Fenwick [EMAIL PROTECTED] | http://perltraining.com.au/
Director of Training
--- Larry Wall [EMAIL PROTECTED] wrote:
Besides $^_ is just uglier than anything else I've seen today...
lol -- I thought of it as a rather cute peeking-wink with a cauliflower
ear, but that's probably much more cutesiness than we want to encourage
in our language design.
A small tangent that might be relevant -- what's the current convention
for, say, putting several related packages in the same file?
In p5, I might write a great Foo.pm that loads Foo::Loader.pm and
Foo::Parser.pm and Foo::Object.pm; I'd usually drop them into seperate
files and have one load
. I'd argue the same is true for parallel.
Paul
--- Jonathan Lang [EMAIL PROTECTED] wrote:
Paul Hodges wrote:
http://perl6.org/doc/design/syn/S02.html still says:
Intra-line comments will not be supported in standard Perl
This is wrong, since S02 also defines intra-line comments, under
Whitespace and Comments. It calls them
Sounds like a good plan to me.
It's one of those bite-sized tasks that will grow with time, but will
make the overall process move along. Feel free to tag me offlist for
help, too.
--- ispyhumanfly [EMAIL PROTECTED] wrote:
chromatic wrote:
On Tuesday 11 December 2007 09:20:22 Paul Hodges
duh. I'll learn to finish reading all the posts before adding my own
*someday*.
--- Darren Duncan [EMAIL PROTECTED] wrote:
At 10:23 AM +0300 12/11/07, Richard Hainsworth wrote:
Darren Duncan wrote:
At 9:04 AM +0300 12/10/07, Richard Hainsworth wrote:
Equally, Something to replace CGI or DBI
It also helps that you consistently make incisive observations and
contributions to conversations, even if they are a little tart
sometimes. :)
But on this general note, is there any current organization or location
where small problems are being parcelled out? I'd love to help, but my
time is
This is another great example of why I love this list. :o]
I live in GA, so far out in the boonies that I can't get cable or
broadband at *all* except for by satellite. I've stopped trying to
explain what I do, because I start saying things like this, and they
glaze and visibly regret it,
on features we didn't need.
Yeah, disk is cheap now, but don't assume everyone has the same
resources, needs, or red tape you have.
Paul
Be a better sports nut! Let your teams follow you
with Yahoo
--- Larry Wall [EMAIL PROTECTED] wrote:
On Tue, Sep 18, 2007 at 07:41:54PM -0700, Paul Hodges wrote:
: while length($ruler) $len; # till there's enough
There is no length function anymore.
duh. I knew that. Still thinking in v5.
Thanks, Larry
--- Adriano Ferreira [EMAIL PROTECTED] wrote:
[[snips here and at end]]
. . . I have one suggestion: you might want to mention
the roundrobin function in the article on the zip function since
the two are very closely related.
Thanks, Joe and Alberto.
Even though the roundrobin is very
length($ruler) $len; # till there's enough
return $ruler; # and returns the string
}
my $r = page_ruler(25); # 0123456789012345678901234
Again, PLEASE double-check my probably goofy syntax.
Paul
--- Adriano Ferreira [EMAIL PROTECTED] wrote:
On 9/18/07, Paul Hodges
a Perl 6 pair.
Paul
How about a Bundle::Common?
Streamline both the core and the inclusion of the most commonly used
modules? The core does include the CPAN module, right?
Personally, I *prefer* grabbing what I need piecemeal, but I understand
making it easy if possible
--- Luke Palmer [EMAIL PROTECTED] wrote:
(aka the executive summary).
Paul
tags ala poddoc and then add the inlined/introspectable documentation for
that particular language.
Now the only hard part is getting the other language designers to allow
ignoring pod markup in their languages. All of the Parrot based variants
could easily incorporate this feature.
Paul
don't get the aesthetics of the Schwartzian Transform,
then you should probably be using python or java anyway, hm?
Let's let Perl be Perl. It's a new Perl, but it's still a pearl. =o)
*Paul
--- Larry Wall [EMAIL PROTECTED] wrote:
On Mon, May 14, 2007 at 02:21:47PM -0400, Ryan Richter wrote
foreach my $item (@items) {
#process each item
} else {
#handle the empty list case
}
What do you think?
I'm not sure if I like it, but there have been several times that I would've
used it recently. I think it would certainly have utility.
Paul
it is spelled a little different with
if ($alpha = $beta) { ... }
When I really meant:
if ($alpha == $beta) { ... }
It is rare though. I think the == vs === will be rare also.
Paul
--shades of PHP.
Taking a page from Template Toolkit.
.keys # same as perl5
.sort # the sorted keys
I know that it isn't quite parallel with Array.sort and it doesn't provide
for .sortkv or .sort pairs, but it might be an option.
Paul
of max or vice versa. My guess
is the operators should win because there could be some low-level shenanigans
that optimize things. But maybe not.
Paul
$a = 1;
($a, undef, my $b) = 1..3;
If you attempted to do
my ($a, undef, $b) you'd get a warn error about re-declaring $a.
Paul
unmodified.
Paul
.
And as for Perl6 - well yes I'd love to see it get here more quickly also.
But I don't think that discussing little nitpicks like this are delaying the
release of Perl6. Maybe they are - but I would guess there are more pressing
issues that are occupying development time.
Paul
the question: If you can do it ugly [1] easily, why not
allow for it do be done prettily [2] ?
say $_ for = if $do_read_input
Paul
[1] It isn't really that ugly - just not as pretty.
[2] Arguably the pretty version is also more ambiguous whereas the ugly
version leaves little room for doubt.
- but will it be under Perl6.
Either way the nested statement modifiers would work even if scopes aren't
introduced at each level.
.say for 1..$_ for 2..5;
I think it reads sort of nicely left to right.
Paul
that the actual useful uses are rare enough to not warrant giving
a feature that could turn hopelessly ugly quickly - even if the current
generation of tools make it easy to add the feature.
Paul
I will abuse it.
Paul
PS. And not that it matters, but TT3 is planned to support nested statement
modifiers and my engine which does much of TT3 already supports them - and I
do use them on occasion - but that's a different mailing list.
it?
Paul Seamons
Section of pge2past.tg that re-writes the expression to be enclosed by an if
block:
transform past (Perl6::Grammar::statement) :language('PIR') {
$P0 = node['statement_control']
if $P0 goto statement_control
$P0 = node['block']
if $P0 goto statement_block
$P0
negatives.
I can't change the mind of Larry but the mind of Larry can be changed. I
can't speak for others, but I have found myself wanting to do similar things
in Perl 5 and I would wager other people have also.
I'll be quiet if you'd like me to be, unless you don't want me to be. :)
Paul
modifier. I don't think
multiple levels introduces any more problem than is already there.
Plus - if there are multiple modifiers then Perl poetry can get even better.
And everybody wins if Perl poetry is better. :)
say I'm ok
if $i_am_ok
if $you_are_ok
while $the_world_is_ok;
Paul
similar to read only strings.
Paul Seamons
I know, shoot me -- but just so we've discussed it and put it to bed,
maybe :if or _if or fi?
shudders
--- Aaron Crane [EMAIL PROTECTED] wrote:
Larry Wall writes:
Maybe we should just make statement modifiers uppercase and burn
out
everyone's eye sockets. :)
I like statement
could be cut down
considerably if all you want to parse is math (no variables).
Paul Seamons
so back to foo(bar). What's the default behavior? String doesn't Num,
does it? though is does convert if the value is good
Does that mean foo(123) should or should not dispatch to foo(Int)?
Or even foo(Num), for that matter Oy, I could see some headaches
around setting these rules in
--- Ashley Winters [EMAIL PROTECTED] wrote:
On 6/2/06, Paul Hodges [EMAIL PROTECTED] wrote:
my @answer = map { async { _() } } @jobs;
That still seems too explicit. I thought we had hyperoperators to
implictly parallelize for us:
my @answer = @jobs.»();
Which would run them
--- Larry Wall [EMAIL PROTECTED] wrote:
On Sat, Jun 03, 2006 at 03:51:45PM -0700, Paul Hodges wrote:
: { no threads;
:print @_.»();
: }
It seems a bit odd to use a construct for its syntactic sugar value
but take away its semantics...
If you just need ordering
--- John Drago [EMAIL PROTECTED] wrote:
You mean is parallel as a synonym for is async?
I think is parallel denotes something as usable by multiple threads
simultaneously, in parallel.
is serial would denote that only one thread can use the $thing at a
time, exclusively.
Are you saying
--- John Drago [EMAIL PROTECTED] wrote:
. . .
class QueueRunner {
our sub process_queue(Code @jobs_in) {
my @ans is serial;
@ans.push map { async { _() } } @jobs_in;
@ans;
}
}
my @answer = QueueRunner.process_job_queue( @jobs );
Actually I think you did
How about one of these?
==
class Baz {
has $.a is restricted;
has $.b is controlled;
has $.c is unique;
has $.d is shared;
has $.e is queued;
has $.f is token;
...
}
--- John Drago [EMAIL PROTECTED] wrote:
I asked this via the Google Groups interface
--- John Drago [EMAIL PROTECTED] wrote:
James Mastros wrote:
I don't like the name synchronized -- it implies that multiple
things are happening at the same time, as in synchronized swiming,
which is exactly the opposite of what should be implied.
Serialized would be a nice name, except
into a
module now, can't it?
So the upshot is, a standardized metamodel seems like the way to go to
me
/my $.02
ot
And Congrats again, gramps. May your new little one be as loved as the
language you've also labored so much to guide to maturity. ;o]
/ot
Paul
on est aisément dupé par ce qu'on aime
activities. PerlNet exists to
provide support for the Perl community, and if there's anything I can do to make
it more suitable to help the Perl 6 effort, then I'd be very happy to do my best
to make it happen.
All the very best,
Paul
--
Paul Fenwick [EMAIL PROTECTED] | http
On Thu, May 04, 2006 at 01:56:44PM +0300, Markus Laire wrote:
On 5/1/06, Paul Johnson [EMAIL PROTECTED] wrote:
But then again, as I said, I really don't see the problem that is being
solved.
This long-dot can be used for many things, not just method calls.
Thanks for taking the time
certianly happens to me fairly often.
Well, I'd obviously quite like that ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
code as much as the next programmer, and probably a
lot more, but I just don't see the need for this syntax which seems
ugly, confusing and unnecessary.
But then again, as I said, I really don't see the problem that is being
solved.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
--- [EMAIL PROTECTED] wrote:
. . .
-Such an eigenmethod is delegated to C.meta just as method like
. . .
+Such an Imetaclass method is always delegated to C.meta just as
changing eigenmethod to Imetaclass method should also change an
to a:
+Such a Imetaclass method is always delegated to
to declare which hash keys or array elements are valid.
Do we have that already?
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
]);
OR assuming I has a Position object and a vector object
move(from = $pos1, delta = $vec1);
The original example just seems difficult to parse.
Paul
)
has %.y is rw; # implies %_y for storage, is virtual
Paul
pick something sane. Here I go speaking for the list, but I
don't think we will find many that think .method syntax breaks in methods if
$_ is rebound as a very sound concept.
Paul
backwards 10
$fh.seek(10, :relative); # from the current location forward 10
$fh.seek(-10, :relative); # from the current location backward 10
Paul
as shorthand for
$fh.pos = $fh.cur + 10`bytes
Likewise for -=
But then that begs the questions of *= (not too nuts), /= (same),
%= (great for fixed length records?) and the predictable other host of
operators.
Am I reaching?
Paul
, programmers shouldn't need to worry about what
optimisations are going on under the covers.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
context is an RFC valid string. Nothing too heavy
there. The time() function is typically only moderately useful without
localtime().
Paul
the
quantified subrule or subpattern to return as an array of CMatch objects?
Paul
.
http://www.mail-archive.com/perl6-language@perl.org/msg11967.html
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
Minor note.
Would you want this:
sub infix:myeq(Str $a, Str $b) { return ($a eq $b) ? $a : ''; }
to be:
sub infix:myeq(Str $a, Str $b) { return ($a eq $b) ? $a but bool::true:
''; }
(Is that the right way to do it ?)
Paul
to the invocant of the method. $^1 refers to the
first invocant. $^ is an alias for $^1. $^n refers to the nth invocant.
Nice and simple. No conflict with existing naming conventions.
Paul
be a way back. In this thread, none of the examples
give one using existing Perl 6 syntax. They are all proposing new ways.
This is one more.
Paul
Paul Seamons wrote:
Yes, I know there can be a way back. In this thread, none of the
examples give one using existing Perl 6 syntax. They are all proposing new
ways. This is one more.
Sorry if this sounded brash. I have a habit of not figuring out that there is
more of the message to read
they are, but maybe that's not such a great
problem.
See http://www.eskimo.com/~scs/C-faq/faq.html, especially sections 3.8
and 11.33 for details.
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
--- David Christensen [EMAIL PROTECTED] wrote:
I'm looking in S09, and reading about junctions. It seems to me
that if we have a junction $j which we use to index into an array
or a hash, it should DWIM and return a junction of the corresponding
values.
@ar=[1..10];
%hash=(a=1,b=4,c=7);
--- Larry Wall [EMAIL PROTECTED] wrote:
On Fri, Apr 15, 2005 at 11:28:31AM -0500, Rod Adams wrote:
: David Wheeler wrote:
:
: But the first person to write [a...] gets what's comin' to 'em.
:
: Is that nothing (since '.' lt 'a'), or everything after 'a'?
Might as well make it
--- Larry Wall [EMAIL PROTECTED] wrote:
. . .
-[a..z]
should be allowed/encouraged/required. It greatly improves the
readability in my estimation. The only problem with requiring .. is
that people *will* write [a-z] out of habit, and we would probably
have to outlaw the - form for
are incremented still
}
%h.say; # values are back to original values
Paul
On Friday 15 April 2005 11:57 am, Juerd wrote:
Paul Seamons skribis 2005-04-15 11:50 (-0600):
my %h = a 1 b 2 c 3;
{
temp %h{$_} ++ for %h.keys;
Just make that two lines. Is that so bad?
temp %h;
%h.values »++;
For the given example, your code fits perfectly. A more common
- the question is about the local (temp) scoping of looping
statement modifiers in Perl6.
Though, I do appreciate your trying to get my example working as is.
Paul
the original question about scoping in the
looping statement modifiers.
Paul
and local currently set the value to
undefined (unless set = to something). I imagine that temp and let will
behave the same.
In which case local %h; and let %h would allocate a new, empty variable in
a addition to the original variable (which is hidden but still retains its
contents).
Paul
as the invocant for most of the time.
Paul Seamons
I'll go back to lurking about now.
eval read :file(foo)
How about:
eval slurp foo;
Paul Seamons
--- David Storrs [EMAIL PROTECTED] wrote:
. . . .
Obviously, however @Larry decide it should be, is the way it'll be
and nothing I can say will change that.
Au contraire -- that's what this list is for.
State your opinion, man! :)
That said: this would suck. Badly.
We should not be
/ above, but after many discussions on
this topic, I'm still not sure if I can.
http://www.nntp.perl.org/group/perl.perl6.language/9576
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
be a full fledged class
which inherits from Some::Module::That::Defines::A::Class. I doubt that it
is optimal - but it does give a little bit of flexibility.
Paul Seamons
'); # index 3 gets 'value'
# which is harder han @array[3] = 'value'
Paul Seamons
On Thursday 19 August 2004 02:14 pm, Paul Seamons wrote:
@array.push(3 = 'value'); # index 3 gets 'value'
Hmm. Well that makes it hard to have an array of pairs - so never mind.
Paul Seamons
--- Austin Hastings [EMAIL PROTECTED] wrote:
. . . .
Of the qualities you listed for Pumpking:
Look, I already told you! I deal with the goddamn customers so the
engineers don't have to! I have people skills! I am good at dealing
with people! Can't you understand that? What the hell is
--- Simon Cozens [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Paul Hodges) writes:
Do note that I realize I can check it. It's just that for no reason
I can quite define, my C background wants a null byte to be FALSE
without any special chicanery on my part when checking. I can live
--- Jonadab the Unsightly One [EMAIL PROTECTED] wrote:
Paul Hodges wrote:
Do note that I realize I can check it. It's just that for no reason
I can quite define, my C background wants a null byte to be FALSE
without any special chicanery on my part when checking. I can live
--- Brent 'Dax' Royal-Gordon [EMAIL PROTECTED] wrote:
Paul Hodges wrote:
--- Spider Boardman [EMAIL PROTECTED] wrote:
You need ord() for character/grapheme/byte/whatever testing that's
equivalent to what C does. Since C doesn't really have strings,
and Perl does, this is just one of those
--- Spider Boardman [EMAIL PROTECTED] wrote:
At some point in history, Paul Hodges wrote (in part):
ph So a null byte is still Boolean true. Ugh, yarf, ack, etc.
No. And it never has been (at least in my world view).
A valid point, though I reply:
my $x = \0;
print true if $x
the more sensible FALSE?
Paul
*
The information transmitted is intended only for the person or entity to which it is
addressed and may contain confidential, proprietary, and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any action
is, will this:
if \0 { print null\n; } # Is this going to print, or not?
And if the answer is because I've somehow botched my syntax, please
correct it and answer the question I obviously *meant* to ask as well?
=o)
Paul
--- Hodges, Paul [EMAIL PROTECTED] wrote:
Every now and then I have
--- 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;} # I assume this won't print.
if undef { print undef\n; } # I
Or for the few Perl emacs people out there:
C-x 8 Y
C-x 8
C-x 8
Paul
On Tuesday 01 June 2004 10:27 am, Gabriel Ebner wrote:
Hello,
Aaron Sherman wrote:
Well, first off my US keyboard doesn't contain it.
Sorry, mistakenly picked an US-International chart.
Second, you're not supposed
--- Larry Wall [EMAIL PROTECTED] wrote:
On Fri, Dec 12, 2003 at 03:10:30PM -0800, Paul Hodges wrote:
: Ok, wait a sec. Does that mean different references to the same
: critter can have differing sets of aspects?
:
: my Dog $Spot;
: my $doggie = Dog.new();
: my $meandog
--- Larry Wall [EMAIL PROTECTED] wrote:
On Sat, Dec 13, 2003 at 07:16:21AM -0800, Paul Hodges wrote:
: $Spot = $visitor.nephew ?? $nicedog :: $meandog;
:
: Which brings up a small side note: that's a successfully applied
: boolean context for $visitor.nephew, right?
Yes
Larry said:
The interesting question to me is what
$ref = \$foo.as(Color);
returns. It looks like a typed reference to me, but it's still
a reference to the object in $foo, or can behave as one somehow.
I don't think it should generate a reference to the bare role,
because roles
--- Jonathan Lang [EMAIL PROTECTED] wrote:
Incidently, I think I've caught on to _one_ of the concepts in the
upcoming object-orientation proposal: linguistically, there's a triad
of basic verbs - namely be, do, and have. If I'm following
things properly, one could think of an object's
How about
use Baz; # assume object type
my property foo;
my @bar of Baz is false but foo; # maybe not what you meant?
If you apply a trait like false to an array, I expect it to apply to the
array instance object itself and not the content, so that
push @bar, Baz.new();
if @bar{
1 - 100 of 206 matches
Mail list logo