Re: [TODO] fill Parrot_register_move() with code : new implementation

On 9/15/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote: Am Donnerstag, 14. September 2006 02:54 schrieb Karl Forner: > Hello, > > So I propose a new implementation that solve the bugs, and that is linear > in space and time, and hopefully produce > an optimal list of moves. It is to be found in t

postgres interface

From: Leopold Toetsch <[EMAIL PROTECTED]> Date: Sun, 24 Sep 2006 20:55:51 +0200 Hi folks, I've started hacking postgres.pir and related stuff. Some remarkable notes: * there's a test now (or the beginnings of it): $ ./parrot t/library/pg.t (the old code didn't even load_

Re: Capture Literals

Jonathan Lang wrote: What got me thinking about this was that I couldn't find decent documentation about Capture literals in the synopses. Are Capture literals going to replace or unify the "assuming"/"currying" behaviors? =Austin

Weekly Perl 6 mailing list summary for 17-23 September, 2006

This week on the Perl 6 mailing lists "`my Yellow sub marine { @we.all.live }`" -- Larry Wall, concluding a series of Beatles references in the grep thread. Language [svn:perl6-synopsis] r12136 - doc/trunk/design/syn Larry Wall committed a change sta

postgres interface

Hi folks, I've started hacking postgres.pir and related stuff. Some remarkable notes: * there's a test now (or the beginnings of it): $ ./parrot t/library/pg.t (the old code didn't even load_bytecode) The test assumes, there's a user's default table. * I've removed the 'PostgreSQL::' pref

Re: A dedicated per-context stack for bsr/jsr/ret

From: Leopold Toetsch <[EMAIL PROTECTED]> Date: Sun, 24 Sep 2006 13:16:08 +0200 Am Sonntag, 24. September 2006 03:43 schrieb Bob Rogers: >The attached patch creates a C in C for > the exclusive use of the C ops. herwise. Is that right? Separating stacks is a good thing, as

Re: Motivation for /+/ set Array not Match?

在 Sep 22, 2006 10:36 PM 時，Patrick R. Michaud 寫到： Out of curiosity, why not: / bar bar $:=(+)/ and then one can easily look at $.from and $.to, as well as get to the arrayed elements? (There are other possibilities as well.) I'm not arguing in favor of or against the proposal, just point

[svn:perl6-synopsis] r12348 - doc/trunk/design/syn

Author: audreyt Date: Sun Sep 24 06:12:58 2006 New Revision: 12348 Modified: doc/trunk/design/syn/S06.pod Log: * S06: Squash two remaining "*f" into "|(f)". Modified: doc/trunk/design/syn/S06.pod == --- doc/trunk/desi

Re: A dedicated per-context stack for bsr/jsr/ret

Am Sonntag, 24. September 2006 03:43 schrieb Bob Rogers: >The attached patch creates a C in C for > the exclusive use of the C ops. herwise. Is that right? Separating stacks is a good thing, as code paths are simplified. Q: do we really want or need a return stack per context? bsr/ret ough