> "a" == autrijus <[EMAIL PROTECTED]> writes:
a> +In numeric context (i.e. when casted into C or C), a Hash object
s/casted/cast/.
i caught this one the other day. looks like the lesson didn't take so we
will have to punish you. you must rewrite pugs in python! MUAHAHAHAHAH!!!
a> +beco
Author: autrijus
Date: Thu Apr 6 01:12:52 2006
New Revision: 8593
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S13.pod
Log:
* S02/S13: s/casted/cast/, as suggested by Uri.
Modified: doc/trunk/design/syn/S02.pod
===
> +If this MMD dispatch succeeds, the result becomes the result of the
> +of the reduce.
"MMD dispatch" ~~ "RAS syndrome"
Also note the two "of the"s.
> +Otherwise, if the MMD dispatch fails, then if there is one argument,
> +while the single argument form can MMD dispatch based on the type of
D
Author: autrijus
Date: Thu Apr 6 01:29:34 2006
New Revision: 8594
Modified:
doc/trunk/design/syn/S03.pod
Log:
* More grammar nits, from Daniel Hulme
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/syn/
HaloO,
[EMAIL PROTECTED] wrote:
* S02: fix the three places where the old form:
$x .(...)
needs to be replaced to the new form:
$x. (...)
-&foo.($arg1, $arg2);
+&foo. ($arg1, $arg2);
What is the reason for this change? I find the
old definition of whitespace before
[EMAIL PROTECTED] skribis 2006-04-05 22:30 (-0700):
> Whitespace is not allowed before the parens, but there is a corresponding
> -C<.()> operator, which allows you to insert optional whitespace before the
> dot:
> +C<.()> operator, which allows you to insert optional whitespace after the
> dot:
Juerd wrote:
+C<.()> operator, which allows you to insert optional whitespace after the dot:
-&foo.($arg1, $arg2);
+&foo. ($arg1, $arg2);
Please reconsider.
We can't. The problem is that:
foo .bar
has to mean:
foo($_.bar)
So the only way to allow whitespace in dot
Damian Conway skribis 2006-04-06 20:41 (+1000):
> >Please reconsider.
> We can't. The problem is that:
> foo .bar
> has to mean:
> foo($_.bar)
> So the only way to allow whitespace in dot operations is to put it after
> the dot.
Given the consequences of this constraint, I think that perh
Randy W. Sims wrote:
Yep, that's ridiculous. I used to see these questions a lot back when I
was answering mails on the beginner groups. People wanting to do things
that have already been done and widely tested, but everyone wants to
write their own in order to "reduce dependencies".
Reinvent
Juerd schreef:
> autrijus:
>> -&foo.($arg1, $arg2);
>> +&foo. ($arg1, $arg2);
> [...]
> Please reconsider.
Yes, please come up with a different character to
bridge/cross/hide/cloak/skip/zap the succeeding "not allowed"
whitespace.
Maybe the "\", making "\" mean "s:s/\s+//".
--
Gr
HaloO,
Damian Conway wrote:
We can't. The problem is that:
foo .bar
has to mean:
foo($_.bar)
So the only way to allow whitespace in dot operations is to put it after
the dot.
The obvious alternative is to make 'foo .bar' simply mean
'call foo and dispatch .bar on the return value'
* David Golden <[EMAIL PROTECTED]> [2006-04-06 13:45]:
>> This underlying behavior is one of my biggest pet peeves with
>> the perl community. Too many people want to go out and write
>> their own version of modules instead of contributing to the
>> work others began.
>
> I suspect that many of th
Subversion logging messages like the one below seem to be flooding this
list right now. May I ask if that's what this list is for?
Best wishes,
Rutger
[EMAIL PROTECTED] wrote:
Author: autrijus
Date: Wed Apr 5 19:08:28 2006
New Revision: 8569
Modified:
doc/trunk/design/syn/S02.pod
doc/t
On Wed, Apr 05, 2006 at 07:24:30PM -0700, Rutger Vos wrote:
> Subversion logging messages like the one below seem to be flooding this
> list right now. May I ask if that's what this list is for?
Well, it gets the people interested in the language design first cut at
the changes being made to the
TSa wrote:
> Note that a prominent, typical foo actually reads:
>
> self .bar;
>
> And a self($_.bar) is pretty much useless. In other words
> wrongly huffmanized.
FWIW, I agree with both points. Some more points:
* I think both "say(.meth)" or ".meth.say" are more succinct/readable
than "sa
On Thu, Apr 06, 2006 at 10:18:48PM +0800, Audrey Tang wrote:
: TSa wrote:
: > Note that a prominent, typical foo actually reads:
: >
: > self .bar;
: >
: > And a self($_.bar) is pretty much useless. In other words
: > wrongly huffmanized.
:
: FWIW, I agree with both points. Some more points:
Larry Wall skribis 2006-04-06 9:01 (-0700):
> Okay, we could revert it, and .foo would remain term/operator sensitive,
> and retroactively eat preceding whitespace when an operator is expected.
Or change the definition so that something that looks like a method
call IS a method call, and that you
[EMAIL PROTECTED] wrote:
We can't. The problem is that:
foo .bar
has to mean:
foo($_.bar)
So the only way to allow whitespace in dot operations is to put it
after the dot.
Damian
I believe Larry's latest updates to Synopses allow for some syntactic
categories to be disabled in
Moin,
On Thursday 06 April 2006 13:42, David Golden wrote:
> Randy W. Sims wrote:
[snip a lot of sensible words]
> I suspect that many of these are API driven. Programming should be fun
> and using an API that doesn't "fit" isn't fun. As a result people go
> write their own stuff that they fe
On 4/6/06, Larry Wall wrote:
On Thu, Apr 06, 2006 at 10:18:48PM +0800, Audrey Tang wrote:
: TSa wrote:
: > And a self($_.bar) is pretty much useless. In other words
: > wrongly huffmanized.
:
: FWIW, I agree with both points.
I agree with those points too, but not necessarily the conclusion.
S
Moin,
On Thursday 06 April 2006 14:59, A. Pagaltzis wrote:
> * David Golden <[EMAIL PROTECTED]> [2006-04-06 13:45]:
> >> This underlying behavior is one of my biggest pet peeves with
> >> the perl community. Too many people want to go out and write
> >> their own version of modules instead of cont
"Ruud H.G. van Tol" schreef:
> Juerd:
>> autrijus:
>>> -&foo.($arg1, $arg2);
>>> +&foo. ($arg1, $arg2);
>> [...]
>> Please reconsider.
>
> Yes, please come up with a different character to
> bridge/cross/hide/cloak/skip/zap the succeeding "not allowed"
> whitespace.
>
> Maybe the "\"
All~
I just noticed something claiming that C<$a. foo()> is actually
C<$a.foo()> (a method call on C<$a>) and that C<$a .foo()> is actually
C<$a $_.foo()> (likely a syntax error).
When did this change? Why did this change?
Also, I liked it better when C<$a .foo()> was a method call on C<$a>.
T
On Thu, Apr 06, 2006 at 01:58:55PM -0400, Matt Fowles wrote:
: All~
:
: I just noticed something claiming that C<$a. foo()> is actually
: C<$a.foo()> (a method call on C<$a>) and that C<$a .foo()> is actually
: C<$a $_.foo()> (likely a syntax error).
:
: When did this change? Why did this change
Larry~
On 4/6/06, Larry Wall <[EMAIL PROTECTED]> wrote:
> On Thu, Apr 06, 2006 at 01:58:55PM -0400, Matt Fowles wrote:
> : All~
> :
> : I just noticed something claiming that C<$a. foo()> is actually
> : C<$a.foo()> (a method call on C<$a>) and that C<$a .foo()> is actually
> : C<$a $_.foo()> (lik
Hi all!
As part of developing Test::Run, I maintain several CPAN modules and install
them to a directory under my home-dir. Now, until today what I did was write
a bash function to run the installation commands ("perl Makefile.PL
PREFIX=$FOO", "make", "make test", make install", or the Module::
On Thu, Apr 06, 2006 at 02:35:53PM -0400, Matt Fowles wrote:
: That makes a good deal of sense. I don't know what I would like more,
: so I guess that I will wait till a more firm consensus is reached.
The current consensus on #perl6 is that, in postfix position only (that
is, with no leading whi
On Thu, Apr 06, 2006 at 12:10:18PM -0700, Larry Wall wrote:
> The current consensus on #perl6 is that, in postfix position only (that
> is, with no leading whitespace), m:p/\.+ \s / lets you embed
> arbitrary whitespace, comments, pod, etc, within the postfix operator.
>
> This allows both the sho
On Thu, Apr 06, 2006 at 03:38:59PM -0400, John Macdonald wrote:
> On Thu, Apr 06, 2006 at 12:10:18PM -0700, Larry Wall wrote:
> > The current consensus on #perl6 is that, in postfix position only (that
> > is, with no leading whitespace), m:p/\.+ \s / lets you embed
> > arbitrary whitespace, commen
I suspect that many of these are API driven. Programming should be fun
and using an API that doesn't "fit" isn't fun. As a result people go
write their own stuff that they feel is easier/faster to use. This is
the flip side of impatience and hubris. E.g. CPAN search found 510
"Simple", 8
Wow, what great timing :)
To add to your use case, on the project I'm currently working on, we
have 5 CPAN-style dists, probably 10 by the time we are done, but they
all need to be installed in a particular order.
Due to the peculiarities of the situation, doing a CPAN::Inject style
setup is
On Thursday 06 April 2006 22:34, Adam Kennedy wrote:
> Wow, what great timing :)
>
> To add to your use case, on the project I'm currently working on, we
> have 5 CPAN-style dists, probably 10 by the time we are done, but they
> all need to be installed in a particular order.
>
> Due to the peculia
Hi,
as far as I see, the Perl* PMCs are no longer used in the Parrot core.
There is still some usage in unmaintained language implementations:
BASIC/compiler unmaintained ?
BASIC/interpreter unmaintained ?
forth unmaintained ?
miniperlunmaintained ?
parakeet
On Thu, Apr 06, 2006 at 01:46:09PM -0700, Bernhard Schmalhofer via RT wrote:
> As PGE nowadays happily works with Parrot standard PMCs, I assume that
> this old issue has been taken care of.
Actually, this particular todo item didn't have anything to do with
PGE. Leo and I were conversing about
On Thu, Apr 06, 2006 at 02:04:06PM -0700, Bernhard Schmalhofer via RT wrote:
> Hi,
>
> as far as I see, the Perl* PMCs are no longer used in the Parrot core.
>
> There is still some usage in unmaintained language implementations:
>
> BASIC/compiler unmaintained ?
> BASIC/interpreter unma
On Thursday 06 April 2006 14:04, Bernhard Schmalhofer via RT wrote:
> 'punie' seems to be the only maintained language implementation using
> Perl* PMCs.
What about Ponie?
> Also some tests and examples are using the Perl* PMCs.
I agree that they probably shouldn't, except for the tests for th
On Apr 6, 2006, at 5:08 PM, Patrick R. Michaud wrote:
On Thu, Apr 06, 2006 at 02:04:06PM -0700, Bernhard Schmalhofer via
RT wrote:
Hi,
as far as I see, the Perl* PMCs are no longer used in the Parrot
core.
Thanks, Bernhard.
There is still some usage in unmaintained language implement
Is parrot broken? I am getting an error that reads,
config.fpmc is truncated.
On 3/27/06, Larry Wall <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 27, 2006 at 02:54:05PM -0600, Jonathan Scott Duff wrote:
> : On Mon, Mar 27, 2006 at 10:46:02PM +0200, Yuval Kogman wrote:
> : > On Mon, Mar 27, 2006 at 14:35:52 -0600, Jonathan Scott Duff wrote:
> : > > I think that if C is the new C,
On 3/27/06, Larry Wall <[EMAIL PROTECTED]> wrote:
> The p5-to-p6 translator will turn
>
> local $x;
>
> into
>
> temp undefine $x;
Are you sure that that's not:
undefine temp $x;
It seems to me that the other way would undefine $x and then temporize it.
Luke
chromatic wrote:
On Wednesday 05 April 2006 14:09, Adam Kennedy wrote:
And now in return, we have new modules that changes the way EVERYBODY
else's code works, and changes the meaning of that code instead, so
Test::MockObject gets less spurious bug reports.
You mischaracterize the situation.
I use 5.8.0 as minimum, but for unicode I think it should be 5.8.1 - but I
am unsure. COuld you give a reason for why specifically 5.8.3?
Actually, in consultation with Audrey and other $experts,
Perl::MinimumVersion applies a 5.8.4 minimum whenever it sees any
mention of Unicode.
I believe
On Thursday 06 April 2006 17:53, Adam Kennedy wrote:
> UNIVERSAL::isa/can when called as a function does a very specific thing,
> and one that is often misunderstood.
... and never correct, in the face of proxy objects, blessed objects,
overloading, and ties.
> And if you were able to distingui
From: Allison Randal (via RT) <[EMAIL PROTECTED]>
Date: Tue, 04 Apr 2006 16:52:49 -0700
# New Ticket Created by Allison Randal
# Please include the string: [perl #38850]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Disp
chromatic <[EMAIL PROTECTED]> writes:
> For various annoying reasons, I can't do it, but running CPD over the code
> could reveal a lot of interesting information:
Done. May I submit the duplications a dupe at a time?
On Apr 6, 2006, at 10:52 PM, Sean Sieger wrote:
chromatic <[EMAIL PROTECTED]> writes:
For various annoying reasons, I can't do it, but running CPD over
the code
could reveal a lot of interesting information:
Done. May I submit the duplications a dupe at a time?
How many are there? I thi
Can you do this? (Forgive synatical errors; I'm a bit behind on this.)
class Foo { has Code:( Str, Str --> Num ) &.somecode }
my Foo $blah .= new :somecode{ $^x cmp $^y }
my Int $x = 2;
my Num $y = Inf;
$blah.somecode( $x, $y );
Does construction of $blah fail because { $^x cmp $^y } d
On Thu, Apr 06, 2006 at 02:49:33PM -0500, Patrick R. Michaud wrote:
> On Thu, Apr 06, 2006 at 03:38:59PM -0400, John Macdonald wrote:
> > On Thu, Apr 06, 2006 at 12:10:18PM -0700, Larry Wall wrote:
> > > The current consensus on #perl6 is that, in postfix position only (that
> > > is, with no leadi
Greetings from Canada,
Selenium Remote Control 0.71 was just released, and it's an awesome
tool for automated functional web testing. Selenium RC is a java*
jar file that launches a combination web server and proxy that allows
you to use perl/python/ruby/java/c# scripts to launch and contr
49 matches
Mail list logo
