Larry,
Thanks for the quick reply.
On Mar 23, 2005, at 1:42 PM, Larry Wall wrote:
This is very much bound up in the meaning of .foo in various contexts,
which we haven't actually nailed down yet. For the moment I would
recommend writing all code with explicit $self.foo or $_.foo until
we figure th
Yuval Kogman writes:
> More!
>
> can you have several slurpy params, of the same type, which are
> assigned contiguous sequences of the thing they can slurp?
>
> foo([EMAIL PROTECTED], *%a, [EMAIL PROTECTED])
> foo(1, 2, 3, a => b, c => d, 4, 5, 6);
>
> for me that makes sense
Here's the responce from the OpenBSD folks. It seems that turning on a
define prior to the atan2() call will set the flags correctly for OpenBSD.
My guess is that NetBSD will behave similarly.
> >Number: 4154
> >Category: library
> >Synopsis: atan2(-0.0, -0.0) returning incor
The two plain subroutine calls C and C with
objects "f isa Foo" and "b isa Bar" are calling the subroutines Foo.foo
and Bar.foo respectively. See the last test in t/pmc/mmd.t.
Not much more will work currently as function signatures are still missing.
The MultiSub object "foo" in the global name
Steve Peters <[EMAIL PROTECTED]> wrote:
> Here's the responce from the OpenBSD folks. It seems that turning on a
> define prior to the atan2() call will set the flags correctly for OpenBSD.
[ ... ]
> _LIB_VERSION = _IEEE_;
Fine. Thanks for the research. It should probably suffice to set
> [leo - Thu Mar 24 07:07:31 2005]:
>
>
> Comments, takers?
>
Since I'm fixing this in Perl, I take a whack at it in Parrot as well.
Steve
On Wed, Mar 23, 2005 at 11:08:17PM +0200, Yuval Kogman wrote:
: On Wed, Mar 23, 2005 at 11:53:06 -0800, Larry Wall wrote:
: > This seems a little backwards--I think all positionals should be bound
: > before you start binding named pairs, if currying is to be consistent with
: > "ordinary" binding.
On Thu, Mar 24, 2005 at 12:58:32PM -0800, Larry Wall wrote:
: Note, the adverbial :{...} is defined as a named binding to the first
: *& parameter (or first *$ parameter if there isn't a slurpy *&), so
: it's already bound by Step C, even if it occurred later syntactically.
Hmm, that's ambiguous,
Larry Wall writes:
> Step A: For each positional parameter, if the next supplied argument is:
>
> 1) a non-pair
> 2) a pair, and this parameter is explicitly declared Pair, or
> 3) a hash, and this parameter is declared Hash, either explicitly,
>or implicitly with a % sigil,
W
In my attempt to get pugs up and running on my machine, I tried to
use the darcs repository. I used a command like...
$ darcs get http://wagner.elixus.org/~autrijus/darcs/pugs/
...which seemed to work without complaining, and applied 699 patches to
my directory. When I try "make" (after fi
--- Larry Wall <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 24, 2005 at 01:17:40PM +0800, Autrijus Tang wrote:
> : As of r1079, there is $?EXECUTABLE_NAME (that is, $^X in perl5) and
> : $?PROGRAM_NAME (that is, $0 in perl5). Note that those two things
> : are unspecced -- I just pulled them out from
On Thu, Mar 24, 2005 at 03:09:37PM -0700, Luke Palmer wrote:
: Larry Wall writes:
: > Step A: For each positional parameter, if the next supplied argument is:
: >
: > 1) a non-pair
: > 2) a pair, and this parameter is explicitly declared Pair, or
: > 3) a hash, and this parameter is de
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #34564]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34564 >
Attached is a patch to clean up pmc2c2.pl and (hopefully) make it more
readable and
Greg Buchholz wrote:
...Well sure enough, there is no Compile.hs in my src/ directory.
Digging around a little bit, I notice that there is a "Compile.hs" in...
http://wagner.elixus.org/~autrijus/darcs/pugs/src/
...but not in...
http://wagner.elixus.org/~autrijus/darcs/pugs/_darcs/current/src/
On Tue, Mar 22, 2005 at 05:18:44PM +0100, Thomas Sandlaß wrote:
: Rod Adams wrote:
: > multi sub postcircumflex::<[ ]>(MyArray $obj : [EMAIL PROTECTED]) is rw
{...}
: >
: >but I'll wait for S14 before speculating further.
:
: Will that ever be written? And if yes, will it be like S13 which
: is b
On Wed, Mar 23, 2005 at 06:58:51PM +0100, Thomas Sandlaß wrote:
: Larry Wall wrote:
: >my @array of Int;
: >
: >is really short for
: >
: >my @array is Array of Int;
:
: How does 'is' relate to 'does'? I mean is the above @array
: ready for operation?
Yes, I think "is" typically implies
On Thu, Mar 24, 2005 at 04:55:52PM -0800, Tupshin Harper wrote:
> I used wget -r to pull down the entire darcs repo, including the working
> directory, and then ran "darcs whatsnew --look-for-adds --summary" to
> generate a list of files that don't seem to have been recorded with
> darcs, and go
On Fri, Mar 25, 2005 at 11:08:11AM +1100, Andrew Savige wrote:
> Thanks Autrijus. I'm sure you have higher priority tasks than this one
> but before I forget, I better note that what is currently returned by
> Pugs $?EXECUTABLE_NAME differs from p5 $^X.
Pugs is first a Golfing System, so there is
So, as now Pugs generates PMC code that makes mandel.p6 run
faster than Perl 5 (http://use.perl.org/~autrijus/journal/23829),
I'm pondering this BEGIN{} mess that Pugs had not dealt with.
Consider this program, example.p6:
use v6;
my $var = BEGIN { say "I'm compiling, man"; time() }
s
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Seems to be another ordering problem, where a hash is used instead of an
> array with inherited vtable methods. pylong.dump has already the wrong
> entry:
>
> 'destroy' => 'default',
>
> in the suoer hash.
I don't think it's an ordering problem (
20 matches
Mail list logo
