At 5:36 PM -0800 11/19/04, Bill Coffman wrote:
Another thing I'd like to do, is throw in is a randomizer, to change
the way the allocator assigns registers. Considering all the cruft
that was uncovered when the algorithm was changed, it might be a good
idea to have a debug feature that selects reg
On Thu, 18 Nov 2004 08:13:02 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Bill Coffman <[EMAIL PROTECTED]> wrote:
> > ps: I'm making progress on grokking the cfg and register renaming
> > stuff. Will let you know.
>
> This needs an SSA graph of the data flow?
Static Single-Assignment (I h
On Thu, Nov 18, 2004 at 04:01:54PM -0700, Patrick R. Michaud wrote:
> 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
# New Ticket Created by chromatic
# Please include the string: [perl #32514]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=32514 >
---
osname= linux
osvers= 2.4.24-benh0
arch= powerpc-linux
cc= gcc 3.2.3 20030422
Sorry for the delay, but here is a revised patch to detect perldoc.
- If Perldoc is detected, no warning messages will be printed and things
will work as before
- If Perldoc is not detected
- Configure.pl will print a message saying that the docs will not
be built
- docs/ will not be buil
On Fri, 19 Nov 2004, Andy Dougherty wrote:
> On Fri, 19 Nov 2004, Dan Sugalski wrote:
>
> > So, if someone'd like to take a shot at thumping the template
> > makefile bits to add in compilers/p6ge to the basic build, that'd be
> > great. Grovelling over the code in there to scrub out portability
>
At 10:58 AM -0500 11/19/04, Andy Dougherty wrote:
On Fri, 19 Nov 2004, Dan Sugalski wrote:
So, if someone'd like to take a shot at thumping the template
makefile bits to add in compilers/p6ge to the basic build, that'd be
great. Grovelling over the code in there to scrub out portability
issues
On Fri, 19 Nov 2004, Dan Sugalski wrote:
> So, if someone'd like to take a shot at thumping the template
> makefile bits to add in compilers/p6ge to the basic build, that'd be
> great. Grovelling over the code in there to scrub out portability
> issues would also be good.
I'll take a look at this
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #32508]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=32508 >
P6GE currently uses a PerlArray for holding an array of captures;
Leo suggests
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #32507]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=32507 >
In P6GE, there's an array (gr_cap) that is used to store group captures
as an a
Gabe Schaffer wrote:
On Wed, 17 Nov 2004 16:30:04 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Gabe Schaffer <[EMAIL PROTECTED]> wrote:
The problem is a different one: the COND_INIT macro just passes a
condition location, the mutex is created in a second step, which isn't
needed for windows. O
Folks,
Since the grammar engine that Patrick's working on is going to be
part of the base parrot kit (given the number of languages that have
perl 5 compatible regex implementations, we might as well make it so
the *real* perl 5, and perl 6, regex engine's there to be used in
their parrot incar
At 8:42 AM -0500 11/19/04, Gabe Schaffer wrote:
On Wed, 17 Nov 2004 16:30:04 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Gabe Schaffer <[EMAIL PROTECTED]> wrote:
The problem is a different one: the COND_INIT macro just passes a
condition location, the mutex is created in a second step, whi
Dan Sugalski wrote:
Hmm, the first thing to take into the account is that return
continuations can be promoted to the fully blown continuations. This
should affect the handlers in the same way - so exception handlers
could have become arbitrary invokable objects at the point when the
exception
On Wed, 17 Nov 2004 16:30:04 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Gabe Schaffer <[EMAIL PROTECTED]> wrote:
> The problem is a different one: the COND_INIT macro just passes a
> condition location, the mutex is created in a second step, which isn't
> needed for windows. OTOH a mutex a
At 10:58 PM + 11/18/04, Tim Bunce wrote:
On Thu, Nov 18, 2004 at 11:37:54AM -0800, chromatic wrote:
On Thu, 2004-11-18 at 13:36 -0500, Dan Sugalski wrote:
> I'd like pushing exception handlers to remain simple -- the current
> system is almost OK. What I'd like it to change to is:
>
>
> [ long win32 proposal ]
>
> I've to read through that some more times.
OK; let me know if you have any questions on how the Win32 stuff
works. I tried to explain things that are unlike POSIX, but of course
it makes sense to me.
> Do you alread have ideas for a common API, or where to split the
At 10:03 AM +0100 11/19/04, Miroslav Silovic wrote:
Dan Sugalski wrote:
It's also important for people writing these things to take into
account the possibility that their exit actions may potentially be
triggered multiple times, courtesy of the joys of continuations.
Hmm, the first thing to tak
Miroslav Silovic <[EMAIL PROTECTED]> wrote:
> Hmm, the first thing to take into the account is that return
> continuations can be promoted to the fully blown continuations.
Yes. But an exception handler is not a RetContinuation object. It's an
Exception_Handler object (also derived from Continuat
Tim Bunce <[EMAIL PROTECTED]> wrote:
> I guess the HLL compiler needs to ensure that for every push the
> control flow will always pass through a matching pop.
Not necessarily. The handler is pushed onto the control stack. During a
context change (e.g. from a subroutine return), the previous cont
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> The 'invoke the current return continuation' op apparently got lost
> in the blowup. That needs to go in.
Its in and named C since yesterday "return with current
continuation".
> I'd like pushing exception handlers to remain simple -- the current
> syste
Dan Sugalski wrote:
It's also important for people writing these things to take into
account the possibility that their exit actions may potentially be
triggered multiple times, courtesy of the joys of continuations.
Hmm, the first thing to take into the account is that return
continuations can
Hello,
by executing the command "perl6 --tree" there is to seen the following
error message:
[EMAIL PROTECTED] perl6]$ perl ./perl6 --tree -e 'print "alf"';
Can't call method "tree" on an undefined value at ./perl6 line 418.
[EMAIL PROTECTED] perl6]$
The problem is that the function $par
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 bi
24 matches
Mail list logo
