Bob Rogers <[EMAIL PROTECTED]> wrote:
>The attached patch is supposed to do two things:
>1. Makes it possible to say ".flatten foo" as part of a
> .pcc_begin_return/.pcc_end_return sequence. Remarkably, this part of
> the patch is only a one-line change; the internals for call & return a
This isn't a bundle. It just provides a list of modules, though I guess
something could parse the Bundle::Phalanx, thanks.
On 20/03/2005 23:43 Andy Lester wrote:
On Mar 20, 2005, at 4:18 PM, Robert Rothenberg wrote:
FYI, I've uploaded Module::Phalanx100 to CPAN in to
$CPAN/authors/id/R/RR/RRWO/
Larry Wall wrote:
On Sat, Mar 19, 2005 at 11:03:40PM +1100, Andrew Savige wrote:
: 2) Documentation.
:Where is the slurp built-in documented? I couldn't find it
:in any of the Synopses (including Rod Adams' recent S29).
:In desperation, I googled and found CPAN Perl6::Slurp.
The officia
On Sun, Mar 20, 2005 at 10:54:15PM -0700, Luke Palmer wrote:
> in the same form if it does come back. So consider 6.0 its usage
> deprecation cycle, so we can redefine its meaning (if we decide to).
I don't see why study needs a deprecation cycle when length doesn't get one.
It seems fair game t
FYI, I've uploaded Module::Phalanx100 to CPAN in to
$CPAN/authors/id/R/RR/RRWO/Module-Phalanx100-0.01.tar.gz
It simply contains a list of the Phalanx distributions from the project
web site at http://qa.perl.org/phalanx/.
It's provided so that anyone who needs a consistent list can use it
rath
Nicholas Clark writes:
> On Sun, Mar 20, 2005 at 10:54:15PM -0700, Luke Palmer wrote:
>
> > in the same form if it does come back. So consider 6.0 its usage
> > deprecation cycle, so we can redefine its meaning (if we decide to).
>
> I don't see why study needs a deprecation cycle when length do
conf/init/hints/msys.pl
Configure::Data->set(
ld => '$(PERL) /bin/perlld',
dynclasses/build.pl
our $LD = qq[$(PERL) /bin/perlld];
test.pl
our $LD = qq[$(PERL) /bin/perlld]; print "'$LD'\n";
our $LD = qw[$(PERL) /bin/perlld]; print "'$LD'\n";
test.pl output:
'0PERL) /bin/perlld'
'$
François PERRAD wrote:
(So with MinGw, the generation of Makefile needs /, and the execution
needs \)
Yes I can confirm this.
MSYS build:
$ perl -Ilib t/pmc/sys.t
1..1
not ok 1 - spawnw, _config
# Failed test (t/pmc/sys.t at line 26)
# got: '. Command not found
# 1
# '
# expected
On Fri, 18 Mar 2005 09:45:57 -0800, Larry Wall wrote:
> I think we'll need to figure out how to shorten $_.foo instead.
It looks short enough to me already. More importantly, its meaning
is immediately obvious.
> Either that, or there has to be a way to explicitly make $_ the
> invocant of a subb
John Macdonald skribis 2005-03-18 12:00 (-0500):
> I've had times when I wanted to be able to use chop at either
> end of a string.
In fact, won't things be much easier if shift and pop workend on strings
as well as on arrays? Now that we have multis, this should be easy to
do.
(For symmetry, thi
Paul Seamons skribis 2005-03-18 9:46 (-0700):
> eval slurp "foo";
That requires foo to have an #line directive (or whatever its Perl 6
equivalent will be) in order to be useful when debugging.
See also http://tnx.nl/include (I want Perl 6 to have this function that
evals a file such that in
I like the t/ directory reorganisation for 6.0.12 and I congratulate
Stevan for the nice README file also. I hope to soon start adding
some tests into this new structure.
Unfortunately, a disagreeable side effect of this reorganisation is
that Pugs 6.0.12 'nmake test' blows up with "command line t
On Tue, Mar 22, 2005 at 01:42:42AM +1100, Andrew Savige wrote:
> Does anyone know the "normal" workaround for this problem?
Later MakeMakers may have fixed that (not sure), but we're targetting
EU::MM 6.17 currently.
> (If not, I could ask the perl-qa folks).
Please do, thanks! :-)
/Autrijus/
On Tue, Mar 22, 2005 at 01:42:42AM +1100, Andrew Savige wrote:
> Unfortunately, a disagreeable side effect of this reorganisation is
> that Pugs 6.0.12 'nmake test' blows up with "command line too long"
> when run under Windows, at least that's what I saw.
>
> Does anyone know the "normal" workaro
Rod Adams <[EMAIL PROTECTED]> wrote:
> Larry Wall wrote:
> > On Sat, Mar 19, 2005 at 11:03:40PM +1100, Andrew Savige wrote:
> >
> > : 2) Documentation.
> > :Where is the slurp built-in documented? I couldn't find it
> > :in any of the Synopses (including Rod Adams' recent S29).
> > :In
On Sun, Mar 20, 2005 at 08:54:54PM -0600, Rod Adams wrote: Okay,
I've come around to liking it, but I think we have to say that 0x,
0d, 0o, 0b, and whatever else we come up with are just setting the
default radix. If a string comes in with an explicit 0x, 0d, 0o,
or 0b, we believe that in preferen
On Mon, Mar 21, 2005 at 03:31:53PM +0100, Juerd wrote:
> [...] (The symmetry is slightly broken, though, because if you push
> "foo" once, you have to pop three times to get it back. I don't think
> this is a problem.))
That's not a new break to the symmetry of push and pop:
@b = (1,2,3);
On Sun, Mar 20, 2005 at 05:27:56PM -0700, Luke Palmer wrote:
: I believe Perl 6 hasn't changed its policy on labels, so you should be
: able to write that in Perl 6. But your behavior might be undefined.
: It's weird to jump into the middle of a loop. We may only allow you to
: jump outwards from
Autrijus,
I un-TODO-ed the tests, and built you a TODO list of what I saw as
outstanding issues. I did my best to differentiate between bugs in the
implementation and un-implemented features.
Enjoy ;)
- Stevan
t/builtins/
- die.t
The stringified version of $! is printing Haskell type information
On Sun, Mar 20, 2005 at 10:33:04PM -0600, Rod Adams wrote:
: I'm thinking C and C should be strictly Code Point level
: activities, but I'm not sure.
Alternately, since Num implies arbitrary precision, we *could* define
a value that can hold as many code points as you like, mod 2**32 or some
such
On Sun, Mar 20, 2005 at 09:08:08PM -0600, Rod Adams wrote:
: Does Perl need a no-op function?
:
: With the addition of "no bare literals", it makes constructs like
:
: 1 while some_func();
:
: an error.
Well, it's not a bareword--it's just potentially a useless use of
the value in a void contex
Andy Lester wrote:
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::Mecha
Larry Wall wrote:
On Sun, Mar 20, 2005 at 09:08:08PM -0600, Rod Adams wrote:
: I propose creating a no-op function "nothing" that can be used
: here or anywhere else you specifically wish to do nothing at all.
:
: given $this {
:when Even { nothing };
:when Prime { ... };
:default
At 12:02 PM +0100 3/15/05, François PERRAD wrote:
When I analyse the failure of t/pmc/sys.t with MinGW32,
I see that this script generates a command depending of the OS
on MSWin32, cmd = ".\parrot temp.imc"
on *nix, cmd = "./parrot temp.imc"
(So with MinGw, the generation of Makefil
At 11:07 AM +0100 3/15/05, Leopold Toetsch wrote:
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
t/pmc/namespace.t
Please have a look at the supported syntax constructs. Are these
sufficient for HLL writers?
Some more thoughts WRT namespaces.
We can define a namespace, where a function or method i
At 5:19 PM +0100 3/19/05, Leopold Toetsch wrote:
1) builtin methods are living in a class namespace e.g.
Float."cos"
ParrotIO."open" # unimplemented
I'm way out of the loop and may have been dealt with in prior mail,
but are we doing real method calls for cos() and suchlike things?
That seem
At 8:10 AM +0100 3/16/05, Leopold Toetsch wrote:
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Syntax proposal:
.sub foo @MULTI
.invocant Integer a
.invocant Float b
.param pmc c
...
Alternate syntax:
.sub foo multi(Integ
On Mon, Mar 21, 2005 at 11:11:58AM -0800, Ofer Nave wrote:
> Interesting idea, but shouldn't POE-based modules stay in the POE namespace?
This is probably not the right place for a prolonged naming discussion,
but why should they? In an ideal world I won't care about the
technology behind the mo
Rod Adams skribis 2005-03-21 14:25 (-0600):
> if $expr {
> nothing;
> }
> is harder to get confused over, IMO
Except writing something when you mean nothing is kind of weird. It
makes sense in rules because it doesn't usually make sense to match
nothingness, but for blocks, I'd hate to see
As everyone's more than aware, I've not been around much at all the
past few months. Real Life, alas, managed to get a good hold on me
and doesn't look to be letting go any time soon. This isn't at all
good for Parrot development -- a designer who's absent is definitely
a Bad Thing, and it's re
Juerd wrote:
Rod Adams skribis 2005-03-21 14:25 (-0600):
if $expr {
nothing;
}
is harder to get confused over, IMO
Except writing something when you mean nothing is kind of weird. It
makes sense in rules because it doesn't usually make sense to match
nothingness, but for blocks, I'd ha
Austin Hastings skribis 2005-03-21 15:55 (-0500):
> I'd like to see nothing as just an alias for {}.
> if $expr
> {
>do nothing;
> }
> Possibly the most clear piece of P6 code ever.
Dangerous, though :)
do nothing if $input =~ /\W/;
system "rm -- $input";
But yes, an alias would
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> As such, I'd like to say a big thanks to Chip Salzenburg who's agreed
> to take the hat. The perl folks on the list will recognize Chip as
> the perl 5.004 pumpking and the guy who took the first shot at "Perl:
> The Next Generation" (aka Topaz). Chip's a d
On Mon, 2005-03-21 at 15:39 -0500, Dan Sugalski wrote:
> And, to forestall some of the wave of questions and off-list
> grumbling: The FAQ!
Q: Is there any way to talk you into continuing to design, or at least
describing, the long-awaited security model?
A: (Chip is a fine choice.)
-- c
At 12:50 PM -0800 3/21/05, chromatic wrote:
On Mon, 2005-03-21 at 15:39 -0500, Dan Sugalski wrote:
And, to forestall some of the wave of questions and off-list
grumbling: The FAQ!
Q: Is there any way to talk you into continuing to design, or at least
describing, the long-awaited security model?
A
On Mon, Mar 21, 2005 at 03:39:57PM -0500, Dan Sugalski wrote:
> As such, I'd like to say a big thanks to Chip Salzenburg who's agreed
> to take the hat. The perl folks on the list will recognize Chip as
> the perl 5.004 pumpking and the guy who took the first shot at "Perl:
> The Next Generation
Hi All,
Is anyone aware of an implementation of Test::Builder/Simple/More and
Test::Harness in JavaScript? The testing scene in JS appears pretty
sad, but I don't want to do much in JavaScript without a nice testing
framework. And Test::More would be my preferred way to go. (Yes, I know
that th
David Wheeler wrote:
Hi All,
Is anyone aware of an implementation of Test::Builder/Simple/More and
Test::Harness in JavaScript? The testing scene in JS appears pretty sad,
but I don't want to do much in JavaScript without a nice testing
framework. And Test::More would be my preferred way to go.
On Mar 21, 2005, at 1:32 PM, Christopher H. Laco wrote:
When you say test JavaScript, what kinds of files are we testing?
Server side web scripting using JavaScript?
Shell scripts files?
And JS that runs in a browser, yes.
Regards,
David
On Mon, 2005-03-21 at 13:27 -0800, David Wheeler wrote:
> Is anyone aware of an implementation of Test::Builder/Simple/More and
> Test::Harness in JavaScript? The testing scene in JS appears pretty
> sad, but I don't want to do much in JavaScript without a nice testing
> framework. And Test::Mo
As described here:
http://www.nntp.perl.org/group/perl.perl6.compiler/413
'nmake test' on the latest release of Pugs blew up under Windows with
"command line too long" (using ActiveState perl-5.8.6).
Is there a "standard" way to fix this? What do other distributions with
vast numbers of tests do
On Tue, Mar 22, 2005 at 09:24:24AM +1100, Andrew Savige wrote:
> http://www.nntp.perl.org/group/perl.perl6.compiler/413
>
> 'nmake test' on the latest release of Pugs blew up under Windows with
> "command line too long" (using ActiveState perl-5.8.6).
>
> Is there a "standard" way to fix this? Wh
According to Dan Sugalski:
> As such, I'd like to say a big thanks to Chip Salzenburg who's agreed
> to take the hat.
I thank you for your kind words, and for giving me the opportunity
again to work long hours and explain difficult and arbitrary design
decisions to enthusiastic contributors. :-)
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Mon, 21 Mar 2005 10:10:31 +0100
Bob Rogers <[EMAIL PROTECTED]> wrote:
> . . .
>Unfortunately, though this patch works as intended, it also has a
> number of bizarre side-effects . . .
> It's remotely conceivable that there'
--- Autrijus Tang wrote:
> Later MakeMakers may have fixed that (not sure), but we're targetting
> EU::MM 6.17 currently.
That is the version I was using.
I asked on perl-qa and Schwern gave a helpful reply, shown below.
I've pushed this thread back to the perl6-compiler list since I assume
autri
Juerd wrote:
Austin Hastings skribis 2005-03-21 15:55 (-0500):
I'd like to see nothing as just an alias for {}.
if $expr
{
do nothing;
}
Possibly the most clear piece of P6 code ever.
Dangerous, though :)
do nothing if $input =~ /\W/;
system "rm -- $input";
But yes, an alias would
46 matches
Mail list logo
