Well, after a long and very fruitful day of hacking, the 'abc'
compiler in Parrot is now written mostly in PGE and NQP, with
all tests passing.
'abc' is an implementation of a basic calculator (like the
unix bc(1) command) for Parrot. While abc does support a lot
of bc features, the primary
On Tue, Nov 27, 2007 at 08:10:15PM +0200, Allison Randal wrote:
Patrick R. Michaud via RT wrote:
On Sun Jul 23 06:35:21 2006, coke wrote:
The TGE grammar doesn't deal with embedded }'s:
Invalid:
transform a (b) {
# do nothing}
}
transform a (b) {
# do {nothing}
}
If we still
On Tue, Nov 27, 2007 at 04:23:17PM -0800, James Keenan wrote:
Attempting 'make realclean' tonight in 2 different sandboxes, both
pointing to trunk, both on Linux, I got the following output:
make -C compilers/tge clean
make[1]: Entering directory `/home/jimk/work/parrot/compilers/tge'
On Tue, Nov 27, 2007 at 08:52:32PM -0800, Will Coleda via RT wrote:
On Wed Apr 04 05:59:18 2007, [EMAIL PROTECTED] wrote:
For me, running the attached PIR file outputs:
Sub
String
instead of:
Sub
Sub
Can anyone reproduce this on the original platform with
0.5.0 or newer? (see
On Tue, Nov 27, 2007 at 08:30:38PM -0800, chromatic wrote:
On Tuesday 27 November 2007 19:49:26 James Keenan wrote:
Since this patch affects 16 configuration modules, I would like to
have it tried out on as many platforms as possible. Reports from
Linux and OpenBSD would be particularly
On Thu, Nov 29, 2007 at 10:20:00AM -0500, Mark J. Reed wrote:
The module could even, I suppose, insert a filter into the compiler so
that your proposed literal syntax would work, but I don't really see
the advantage of that over this:
my $doc = Document.new(END);
I should also note that the problem is related to the :outer
somehow, because if we remove :outer from the definition of 'foo'
in x.pir then everything works as expected:
$ ./parrot y.pir
compiler start
reading x.pir into $S0
compiling (but not running) $S0
XYZ::BEGIN
done
On Wed, Nov 28, 2007 at 11:22:30AM -0800, James Fuller wrote:
# New Ticket Created by James Fuller
# Please include the string: [perl #47926]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47926
after building
On Thu, Nov 29, 2007 at 06:17:57PM -0800, chromatic wrote:
On Thursday 29 November 2007 18:05:32 Patrick R.Michaud wrote:
Yes, that subject line is correct -- I've found a bug
that shows itself _only_
- when I build Parrot using ccache,
- for one seemingly obscure json test,
On Fri, Nov 30, 2007 at 08:07:30AM +0200, Allison Randal wrote:
Will Coleda wrote:
1) using getclass (aka, reject this ticket)
2) doing something custom for the say method here (like, say,
translating say 'what' into something like getstdout P0;
P0.'say'('what');
3) eliminating the
On Sat, Dec 01, 2007 at 01:45:57PM -0800, Will Coleda wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #48010]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=48010
print_newline
On Sat, Dec 01, 2007 at 02:30:24PM -0800, Will Coleda wrote:
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=48020
from DEPRECATED.pod
=item Bfind_name
There are several variants of some of the above ops; all are deprecated,
and are replaced by the ops
On Sun, Dec 02, 2007 at 10:44:08AM +0100, Paul Cochrane wrote:
NQP and Perl6 aren't Perl5; Should we really be running the perl5 coding
standard tests against them?
Probably not, but having the correct coda is a good thing, ...
Agreed.
... and I only
needed to switch off the warnings
On Mon, Dec 03, 2007 at 12:20:02PM +, Smylers wrote:
cdumont writes:
I don't really think using the column in a ternary means that you
cannot use it else where.
We started off with that, and it was changed specifically because it was
causing a problem; I can't remember exactly what,
On Tue, Dec 04, 2007 at 12:54:43PM -0500, istarex wrote:
Is it possible to compile a single PGE grammar against multiple sets
of actions to get multiple different parsers? This would be good for
Lisp-like languages where you have one parser that spits out PIR code
and a parser that is invoked
On Fri, Dec 07, 2007 at 08:45:03PM +0200, Allison Randal wrote:
jerry gay wrote:
looks good to me. commit away!
nice work.
I've got a clean report on our core platform targets, so committed in
r23574. As usual, please report any issues.
r23574 gives me failures in t/src/vtables.t and
On Sun, Dec 09, 2007 at 10:36:19AM -0600, Jonathan Scott Duff wrote:
I understand that | and || may not actually be differentiated in
implementation yet, but they do different things according to the spec.
I've attached a patch for NQP to change | to || in places where I think it
On Wed, Dec 12, 2007 at 09:16:46AM -0700, Kevin Tew wrote:
I'm using this code to dump PGE parse trees in Perl5 dump format.
Can it get modified/added to HLLCompiler and PCT?
I'm using it for a research project where the compiler is written in Perl5.
The compiler translates the PGE parse
On Sat, Dec 15, 2007 at 05:45:56PM +0200, Allison Randal wrote:
Patrick R. Michaud via RT wrote:
Yes, I didn't quite expect anyone to be using PCT::HLLCompiler with
PAST-pm, or supplying their own PAST-POST transformation.
If we need to put the ostgrammar back into the HLLCompiler, we can
While at a meeting today I had a period of time where I couldn't
easily sync with the Parrot repository to work on it, so I hacked
together a small script to automatically populate a new languages/
subdirectory with a standard compiler tools setup. The script
is attached.
With this script, one
On Sun, Dec 16, 2007 at 05:09:15AM -0800, Bernhard Schmalhofer wrote:
In compilers/pct/src/PAST/Compiler.pir there is support for the pasttype
'chain'.
However I could not find it in docs/pdds/pdd26_ast.pod.
So, should documentation of 'chain' be added to PDD26?
Sure. Part of the
On Mon, Dec 17, 2007 at 10:24:25AM +0100, Paul Cochrane wrote:
On 17/12/2007, chromatic [EMAIL PROTECTED] wrote:
After fixing a few small tests, fulltest passes everything but a couple of
in-progress coding standards tests on my platform. The release is ready on
the world's most lenient
On Tue, Dec 18, 2007 at 03:52:39PM +0200, Allison Randal wrote:
Patrick R.Michaud (via RT) wrote:
This ticket is asking for some convenient mechanism to have
a :method be automatically entered as a sub in the namespace.
This used to be the situation prior to the pdd15oo merge,
and I've come
This is a longish message describing some obstacles I'm
encountering with implementing eval() in perl6, especially
as it relates to handling of lexical (my) variables. IIRC
there are quite a few tests in the Perl 6/Pugs test suite
that expect a working eval(), so we may need this capability
On Wed, Dec 19, 2007 at 11:15:46PM +0100, Mehmet Yavuz Selim Soyturk wrote:
One temporary workaround that I considered for this problem
would be to have eval() use introspection on its caller to
create a wrapper sub that duplicates the lexical environment of
the caller, and then use that
On Wed, Dec 19, 2007 at 10:57:27PM -0600, Patrick R. Michaud wrote:
On Wed, Dec 19, 2007 at 11:15:46PM +0100, Mehmet Yavuz Selim Soyturk wrote:
One temporary workaround that I considered for this problem
would be to have eval() use introspection on its caller to
create a wrapper sub
On Thu, Dec 20, 2007 at 09:20:22AM +0200, Allison Randal wrote:
Patrick R. Michaud wrote:
Of course, in the previous object model I think there was only
one place to look, and find_method did the searching.
In the previous model, there was no distinction between subroutines and
methods
Since the perl6 compiler on Parrot is moving ahead nicely in
its new incarnation, it's time for us to start looking at the
official test suite again. As a reminder, Pugs is considered
the repository for the official test suite at the moment
( http://svn.pugscode.org/pugs/t/ ).
Having looked at
On Thu, Dec 20, 2007 at 11:35:44AM -0600, Jonathan Scott Duff wrote:
On Thu, Dec 20, 2007 at 11:23:05AM -0600, Jonathan Scott Duff wrote:
Adriano answered #1 I think: $yaml = Q:!c{ $key: 42 };
Er, I just looked over the spec again and realized that Q does
absolutely no interpolation, so it
On Thu, Dec 20, 2007 at 06:01:53PM -0500, Mark J. Reed wrote:
On Dec 20, 2007 4:30 PM, Patrick R. Michaud [EMAIL PROTECTED] wrote:
Just to add another perspective, PHP uses curlies inside of
double-quoted strings to indicate various forms of
interpolation, and it doesn't
On Fri, Dec 21, 2007 at 01:30:42AM -0700, Kevin Tew wrote:
I'm working on http://rt.perl.org/rt3/Ticket/Display.html?id=48631
I've added parsing of :namespace to imcc, now I'm trying to figure out
what I'm suppose to do differently when :namespace is present in a
methods prototype.
I
Kevin Tew started investigating this ticket, and he discovered
that :method subs are already being placed as entries in the
namespace by default, which is the behavior I was looking for.
So, the issue turns out to be a non-issue (for me at least),
unless we decide to make it one.
Apologies
On Thu, Dec 27, 2007 at 07:15:40PM +0200, Allison Randal wrote:
With autoboxing/unboxing, there's not really a need to differentiate
between the PMC Integer/String/Float types and the I/S/N registers.
Coming into this discussion from the middle (and having not read
pdd15 in great detail),
On Thu, Dec 27, 2007 at 07:26:30PM +0200, Allison Randal wrote:
Agreed. (It's worth noting that the problem existed before :invocant was
added.) Adding :invocant, and giving it a string parameter, means we
could do away with the list of types on the :multi flag (we'd still need
the :multi
On Thu, Dec 27, 2007 at 07:56:35PM +0200, Allison Randal wrote:
Patrick R. Michaud wrote:
On Thu, Dec 27, 2007 at 07:15:40PM +0200, Allison Randal wrote:
With autoboxing/unboxing, there's not really a need to differentiate
between the PMC Integer/String/Float types and the I/S/N registers
On Thu, Dec 27, 2007 at 07:45:03PM +0200, Allison Randal wrote:
Patrick R. Michaud wrote:
On Thu, Dec 27, 2007 at 07:26:30PM +0200, Allison Randal wrote:
Agreed. (It's worth noting that the problem existed before :invocant was
added.) Adding :invocant, and giving it a string parameter, means
On Fri, Dec 28, 2007 at 12:37:56PM -0800, chromatic wrote:
On Friday 28 December 2007 04:15:03 Will Coleda wrote:
My concern here is HLL interop. I think it would be cleaner to specify
the base types ( or perhaps a does ) to be generic enough to let
another language invoke your multis.
On Fri, Dec 28, 2007 at 08:09:23PM -0600, John M. Dlugosz wrote:
At present this isn't possible, the best we can offer is
/path/to/parrot/parrot /path/to/parrot/languages/perl6/perl6.pbc
hello.pl, which is a pain. So, we need a way to package this up into a
simple shell script,
On Sun, Dec 23, 2007 at 06:01:22PM -0800, Stephen Weeks wrote:
Working on getting parrot to parse the lojban grammar, I found that it
would hang forever with --target=parse. Tracked it down to a ws rule.
When I define a custom token ws in the grammar, it parses without
problem.
Built a
On Mon, Dec 24, 2007 at 05:12:24PM -0800, Christopher Pruden wrote:
# New Ticket Created by Christopher Pruden
# Please include the string: [perl #49085]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49085
On Fri, Dec 28, 2007 at 07:11:23PM -0800, chromatic wrote:
On Friday 28 December 2007 16:16:55 Patrick R.Michaud wrote:
Whenever a PAST::Op node gets a non-PAST child, PCT currently
throws a cryptic exception message like:
Method 'named' not found for invocant of class 'Perl6::Grammar'
On Sat, Dec 29, 2007 at 12:04:09PM +0200, Allison Randal wrote:
Patrick R.Michaud (via RT) wrote:
Whenever a PAST::Op node gets a non-PAST child, PCT currently
throws a cryptic exception message like:
Method 'named' not found for invocant of class 'Perl6::Grammar'
A better exception
On Sat, Dec 29, 2007 at 11:29:46AM +0200, Allison Randal wrote:
Patrick R.Michaud (via RT) wrote:
* add some smarts to Parrot to allow it to search/execute .pbc files
in some standard locations (RT#47992)
We certainly need to allow configurable search paths (at runtime and
compile-time).
On Sat, Dec 29, 2007 at 12:13:19PM -0800, chromatic wrote:
On Saturday 29 December 2007 01:29:46 Allison Randal wrote:
* convert perl6.pbc into a C executable
Possible, but ultimately too constraining. There are significant
advantages to having the full Parrot runtime environment
On Mon, Dec 31, 2007 at 11:17:53PM +0300, Richard Hainsworth wrote:
Not sure whether this should be p6-lan or p6-users. Posted to p6l only.
Since the question is specific to perl6 and Parrot, it probably
belongs on perl6-compiler. But I'll answer it here for now,
as it may spark a language
On Wed, Jan 02, 2008 at 09:58:21AM +0100, Paul Cochrane wrote:
I've been seeing this problem off and on for over a month. As you've
noticed, it's rather intermittent, however, when the problem occurs it
persists for up to couple of hours. I've also seen that this is
platform independent, and
On Tue, Jan 01, 2008 at 11:15:57PM -0800, Andy Lester wrote:
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49296
perl6 -esay 'hello world' should work.
Oddly(?), the question of standard options to Perl 6 implementations
also came up in today's Perl 6 design meeting. I believe Larry
On Tue, Jan 01, 2008 at 11:15:07PM -0800, Andy Lester wrote:
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49292
The -h should provide a list of help.
See also the comments about Perl 6 standard command line options
in RT#49296.
Pm
On Tue, Jan 01, 2008 at 11:15:34PM -0800, Andy Lester wrote:
# New Ticket Created by Andy Lester
# Please include the string: [perl #49294]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49294
perl6 -v should
On Thu, Jan 03, 2008 at 12:39:54PM -0800, chromatic wrote:
On Thursday 03 January 2008 12:05:48 [EMAIL PROTECTED] wrote:
-# Copyright (c) 2007, The Perl Foundation
+# Copyright (C) 2001-2008, The Perl Foundation.
# $Id$
I'm not sure this is legal. Certainly TPF holds a copyright on
On Thu, Jan 03, 2008 at 09:40:23PM -0500, Bob Rogers wrote:
From: Patrick R. Michaud via RT [EMAIL PROTECTED]
Date: Wed, 02 Jan 2008 22:29:35 -0800
On Wed Jun 20 16:23:40 2007, pmichaud wrote:
On Thu, Jun 21, 2007 at 12:08:33AM +0100, Jonathan Worthington wrote
On Fri, Jan 04, 2008 at 12:55:19AM -0600, Andy Lester wrote:
http://use.perl.org/~pmichaud/journal/35272
http://perlbuzz.com/2008/01/flurry-of-perl-6-activity-picks-up-new-contributor.html
Lots of cool stuff is going on, and I'm so so glad to see it. I'm
thinking of making a Perl
On Fri, Jan 04, 2008 at 07:43:18PM -0800, chromatic wrote:
I just ran a little experiment. I patched Parrot::HLLCompiler to transcode
the source code it reads to UCS-2 before parsing and compiling it, then I
profiled building perl6.pbc.
Without this hack, the build takes around 20
On Sat, Jan 05, 2008 at 12:29:40AM -0600, Patrick R. Michaud wrote:
On Fri, Jan 04, 2008 at 07:43:18PM -0800, chromatic wrote:
(Callgrind suggests that about 45% of the running time of
the NQP part of the build comes from utf8_set_position
and utf8_skip_forward.)
Even better might
On Sat, Jan 05, 2008 at 01:09:01AM -0600, Patrick R. Michaud wrote:
On Sat, Jan 05, 2008 at 12:29:40AM -0600, Patrick R. Michaud wrote:
On Fri, Jan 04, 2008 at 07:43:18PM -0800, chromatic wrote:
(Callgrind suggests that about 45% of the running time of
the NQP part of the build comes
On Sat, Jan 05, 2008 at 12:17:00PM +0100, Cosimo Streppone wrote:
Patrick wrote:
[...] I also improved utf8_set_position
a bit so that it doesn't always have to restart position
counting from the beginning of the string. As a result,
compiling the actions.pl script on my machine goes from
On Wed, Sep 01, 2004 at 01:07:49PM -0700, Larry Wall wrote:
On Wed, Sep 01, 2004 at 01:57:32PM -0400, Dan Sugalski wrote:
: I promised Patrick this a while back but never got it, so here it is.
:
: This is a list of the semantics that I see as needed for a regex
: engine. When we have 'em,
On Fri, Sep 03, 2004 at 02:44:52PM -, Chip Salzenberg wrote:
According to [EMAIL PROTECTED] (Dan Sugalski):
*) extract substring
Rather than that, wouldn't you prefer to make substring of target
string the actual target of all these?
Yes, yes, yes, this would be far more useful.
Pm
On Tue, Sep 07, 2004 at 04:11:18PM +, Herbert Snorrason wrote:
So ... it's actually happening? There's really going to *be* a Perl6?
It's not just an april fool's gone wrong, like Parrot? ;)
Mark my words: There will be a Perl 6.
Pm
On Wed, Sep 08, 2004 at 10:48:05AM +, Herbert Snorrason wrote:
In the interest of a layman's curiosity: What's the current status?
We're in the beginning stages of building a basic perl 6 grammar engine
(i.e., probably without p6 closures) that compiles to parrot and handles
basic
On Wed, Sep 08, 2004 at 07:53:07AM -0700, Gregory Keeney wrote:
Patrick R. Michaud wrote:
We're in the beginning stages of building a basic perl 6 grammar engine
(i.e., probably without p6 closures) that compiles to parrot and handles
basic optimizations. Concurrent with that I'm working
On Wed, Sep 08, 2004 at 09:56:12AM -0700, Larry Wall wrote:
On Wed, Sep 08, 2004 at 07:33:45AM -0600, Patrick R. Michaud wrote:
: We're in the beginning stages of building a basic perl 6 grammar engine
: (i.e., probably without p6 closures) that compiles to parrot and handles
: basic
On Wed, Sep 08, 2004 at 09:19:51AM -0700, Jared Rhine wrote:
[Herbert == [EMAIL PROTECTED] on Wed, 8 Sep 2004 15:18:27 +]
Herbert And any way for an overeager newbie to help?
The classic answer is write tests. [...] Just by browsing
lists archives, in a few days, you could
On Wed, Sep 08, 2004 at 02:35:21PM -0400, JOSEPH RYAN wrote:
From: Dan Sugalski [EMAIL PROTECTED]
Or we could just get closures working...
To get closure assertions working, you need
something that compiles the code in the
closure assertion, and so there is a bit of a
bootstrapping
On Tue, Sep 14, 2004 at 04:03:49PM +0200, James Mastros wrote:
Or, instead of thinking of this as a special-purpose thing, consider
rules to be a sepperate language from perl, mostly independent of it,
and the /default/ language for assertations/rules being perl, but allow
a :language
On Tue, Sep 14, 2004 at 08:43:08AM -0700, Larry Wall wrote:
I'd suggest looking at the t/op/re_tests file from Perl 5. It's based
on the test suite that originally came with Henry Spencer's regular
expression package. It would, of course, need to be translated and
extended, but it contains a
On Tue, Sep 14, 2004 at 12:42:59PM -0700, Larry Wall wrote:
: Of course, this is really language design -- Larry, you listening?
Sure, I'm listening, but what's the point when I agree with everyone. :-)
I agree that the default should be the current outer language.
I agree that the
On Fri, Sep 17, 2004 at 11:44:09AM +0200, James Mastros wrote:
Or is there some syntactic shortcut that can be made to let us find
the end of a closure without having to fully parse the closure itself?
Well, we could do that for the time being, in which case, I suggest the
end condition be
On Fri, Sep 24, 2004 at 11:36:43AM -0500, Rod Adams wrote:
Output would be a step by step graph of the internal logic used to match
/ not match the string. I'd break the RE up into the same pieces the
Engine does, then show how that subrule matched char a, then char b, but
failed to match
On Fri, Oct 29, 2004 at 11:03:04AM -0700, [EMAIL PROTECTED] wrote:
It was my understanding that Patrick Michaud was working on the Perl 6
grammar and after that was done, the work on the actual compiler would
commence. I've checked http://dev.perl.org/perl6/ and I don't see any
more
Does Parrot have anything available (yet?) for testing membership in
character classes-- things like isspace, isupper, islower, etc?
I searched around a bit in the docs, online references, and P6PE
and found very little about it.
How about for creating and manipulating character classes?
On Wed, Nov 17, 2004 at 10:03:14PM +0100, Leopold Toetsch wrote:
As already stated, I don't consider these as either light-weight nor
faster. Here is a benchmark.
Below are 2 version of a recursive factorial program. fact(100) is
calculated 1000 times:
PIR 1.1 s
bsr/ret
On Wed, Nov 17, 2004 at 10:03:14PM +0100, Leopold Toetsch wrote:
Dan Sugalski wrote:
As already stated, I don't consider these as either light-weight nor
faster. Here is a benchmark.
Below are 2 version of a recursive factorial program. fact(100) is
calculated 1000 times:
PIR
On Wed, Nov 17, 2004 at 11:07:28PM +0100, Leopold Toetsch wrote:
$ parrot pmfactbsr.imc
500500
3.459947
$ parrot -Oc pmfact.imc
500500
1.237185
Now what ;)
Are you sure, that you can't do a tailcall sometimes?
Sure, p6ge already makes heavy use of tailcalls. In a bsr/ret scheme,
the
On Wed, Nov 17, 2004 at 10:35:47PM +, Nicholas Clark wrote:
On Wed, Nov 17, 2004 at 02:47:09PM -0700, Patrick R. Michaud wrote:
BTW, it may be very possible for me to write the p6ge generator so
that it can be switched between the PIR and bsr/ret calling conventions,
so we don't need
I've just committed the first draft of a Perl 6 grammar engine to
the parrot repository (in compilers/p6ge). What you'll find there
is still at a somewhat early stage of development, I'm releasing it
now so that people can begin commenting and suggesting improvements
to the framework.
The next
On Fri, Nov 19, 2004 at 07:52:57AM -0500, William Coleda wrote:
oolong:~/research/parrot/compilers/p6ge coke$ make
cc -I ../../include -c -o p6ge_parse.o p6ge_parse.c
p6ge_parse.c:23:20: malloc.h: No such file or directory
Oops. Should've been stdlib.h instead. Fixed, thanks.
make: ***
On Fri, Nov 19, 2004 at 09:05:31AM -0500, Dan Sugalski wrote:
At 7:00 AM -0700 11/19/04, Patrick R. Michaud wrote:
One of the areas where we can definitely use assistance is
in porting and testing p6ge in operating environments different
from the ones I have available to me--currently I'm
On Fri, Nov 19, 2004 at 02:54:20PM +0100, Leopold Toetsch wrote:
Well, p6ge should eventually use Parrot's config info and the Makefile
ought to be a generated one.
s/eventually use/be using/# :-)
Dan's moved the item to p6i, so hopefully someone there will either
make the changes for me
On Fri, Nov 19, 2004 at 07:03:45AM -0800, Will Coleda wrote:
This would be a good idea. pmc's fix for the malloc.h issue gets the error
below.
All the CC flags (and file extensions, and path separator)
should be pulled from config.
Also, missing a clean target.
(Sorry if it sounds
Just a quick note to perl6-compilers that I've just committed
a patch (timely submitted by Andy Dougherty) that should enable
p6ge to compile under OSX and a few other environments a bit
more cleanly. More details to come soon.
Pm
- Forwarded message from Patrick R. Michaud [EMAIL
On Sat, Nov 20, 2004 at 12:18:17AM +, Nicholas Clark wrote:
$ ../../parrot demo.pir
input /pattern, string to match, + to continue match, ? to print pir,
/
Unrecognized character at offset 1 (found '')
Segmentation fault
Is this a known limitation? [Done after Andy's patch went in]
Is there some opcode or function built into the standard parrot
distribution that will print a string with appropriate escapes
around special characters (i.e., display newlines as '\n',
returns as '\r', non-printable characters as '\xnn' or '\nnn', etc.)?
I can certainly write a function to do
On Mon, Nov 22, 2004 at 02:40:00AM -0500, William Coleda wrote:
I'll be able to use this to implement quite a few items missing from
ParTcl, and those updates should hit CVS in the next week or so.
Great, I'm hoping there's enough of p6ge present to really help.
There are still quite a few
On Sun, Nov 21, 2004 at 07:48:03PM +0100, Leopold Toetsch wrote:
William Coleda [EMAIL PROTECTED] wrote:
Data::Escape is probably your best bet.
Good bet, thanks.
.sub _main
load_bytecode runtime/parrot/library/Data/Escape.pbc
^^^
Just drop that prefix -
As of a few minutes ago, the Perl 6 Grammar Engine has been
renamed to the Parrot/Perl Grammar Engine (PGE). All of the associated
files and symbols have been likewise renamed, and some things have
been moved around to more closely follow Parrot guidelines.
The README file in compilers/pge has
On Sun, Nov 28, 2004 at 01:33:08AM -0500, William Coleda wrote:
A few issues with the recent CVS doings...
1) runtime/parrot/library/runtime/PGE.pir doesn't compile by default. Which
it can't, because:
2) PGE doesn't build by default. Should it? If so, then...
Eventually PGE should build
I'm reviewing the updated S05 (2 Dec 2004) and ran across this
in the Hypothetical Variables section:
# Pairs of repeated captures can be bound to hashes:
/ %options := [ (ident) = (\N+) ]* /
Actually, I see three captures there, so should this instead read...?
/ %options
On Wed, Dec 08, 2004 at 08:19:17AM -0800, Larry Wall wrote:
And people would have to get used to seeing ? as non-capturing assertions:
?before ...
?after ...
?ws
?sp
?null
This has a rather Ruby-esque I am a boolean feeling to it. I think
I like it. It's pretty easy
On Thu, Dec 09, 2004 at 10:52:54AM +, Matthew Walton wrote:
Of course, it then begs the question about
word ws $foo ws number
if we're thinking of parallels with qw//-like constructs, which I
certainly am. I'm not quite sure what that would do, as it collides
slightly with the
On Wed, Dec 08, 2004 at 08:24:20PM -0800, Ashley Winters wrote:
I was working on the (possibly misguided) assumption that there's a
cost to capturing, and that perhaps agressive capturing isn't worth
having on in a one-liner. Some deep part of my mind remembers $`
being bad, I think. If
On Fri, Dec 10, 2004 at 08:50:46PM +0100, Leopold Toetsch wrote:
We need language lawyers ;)
IANAL, but I am a mathematician.Because Cxor necessarily always
depends on *both* its arguments, analogies with Cand and Cor are
inappropriate.Cxor cannot short-circuit, and it is not
On Sat, Dec 11, 2004 at 04:42:54AM +0100, Leopold Toetsch wrote:
Patrick R. Michaud [EMAIL PROTECTED] wrote:
Just as Cor returns its first non-false argument, the interpretation
of Cxor would be that it returns its single non-false argument, or 1 if
both (all?) arguments logically
On Tue, Dec 14, 2004 at 10:49:31AM -0500, Dan Sugalski wrote:
Yes. I'll presume that the first Perl6 compiler will just emit closures
for each block.
Ah, I hope not. I *really* hope not. (Paying attention Patrick? :)
That'd be rather slower than necessary in most cases.
Yup, I'm paying
On Fri, Dec 17, 2004 at 10:21:40AM +0200, Markus Laire wrote:
I'm currently writing few tests for PGE. So far I've found 2 failing
tests: (with parrot_2004-12-16_160001.tar.gz)
p6rule_like('abcabbc', 'ab+?bc', qr/0: abbc @ 3/, '');
p6rule_like('abbcabbbc', 'ab+?', qr/0: ab @ 0/, '');
On Fri, Dec 10, 2004 at 01:34:03PM -0500, James deBoer wrote:
Currently, the split opcode is declared as 'split(out PMC, in STR, in
STR)' where $2 is a regex.
PGE, however, currently supports three types of regular expressions, and
more are likely going to be added. So, which type of
On Sat, Dec 18, 2004 at 12:16:31PM +0200, Markus Laire wrote:
This test seems to cause an infinite loop
(with parrot_2004-12-16_160001)
p6rule_isnt('a--', '^[a?b?]*$', 're_tests 387 (#438)'); # infinite loop
So far repeating groups of zero-length strings causes an infinite loop-
I just
On Sat, Dec 18, 2004 at 08:47:42AM -0800, Larry Wall wrote:
: This test seems to cause an infinite loop
: (with parrot_2004-12-16_160001)
:
: p6rule_isnt('a--', '^[a?b?]*$', 're_tests 387 (#438)'); # infinite loop
Detecting failure to progress can be quite tricky, actually. It's easy
On Sat, Dec 18, 2004 at 09:49:32PM +0200, Markus Laire wrote:
Here are 700 tests for pge, autoconverted from 're_tests' file, from
perl5 source.
If there are any significant errors in these tests, please tell, and I
can correct the script. Original perl5-tests are in comments so it's
On Mon, Dec 20, 2004 at 01:59:57PM +0200, Markus Laire wrote:
I was wondering if it would make sense to add the original 're_tests'
file to parrot distribution, with a script which autogenerates
're_tests.t' from it. This way it would be possible to update the script
if testing-format is
501 - 600 of 2011 matches
Mail list logo
