hi,
I made some additional changes to PDD16:
* added an example to do a callback. I left in the "old" explanation,
but Im' not sure how much of that is still relevant.
* small text improvements wrt example nci
* removed "CHANGES" section: it was just duplicating the history
section. This PDD
On Monday 26 February 2007 01:34, Klaas-Jan Stol wrote:
> I made some additional changes to PDD16:
>
> * added an example to do a callback. I left in the "old" explanation,
> but Im' not sure how much of that is still relevant.
> * small text improvements wrt example nci
> * removed "CHANGES" sect
chromatic wrote:
On Monday 26 February 2007 01:34, Klaas-Jan Stol wrote:
I made some additional changes to PDD16:
* added an example to do a callback. I left in the "old" explanation,
but Im' not sure how much of that is still relevant.
* small text improvements wrt example nci
* removed "C
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Feb 26 14:00:04 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
hi,
I've done some more work on the grammar of Pynie.
This patch also includes the other patch I sent yesterday (so that one
can be skipped).
This grammar is ALMOST done, but now I'm kinda stuck, because there is
some infinite recursion :-(
It would also need some cleanup, and of course test
# New Ticket Created by Jerry Gay
# Please include the string: [perl #41623]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41623 >
pge's syntax for specifying ops to the op precedence parser should
follow the perl 6 spec i
On Mon, Feb 26, 2007 at 07:09:58AM -0800, Jerry Gay wrote:
> # New Ticket Created by Jerry Gay
> # Please include the string: [perl #41623]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=41623 >
>
>
> pge's syntax for s
On Mon, Feb 26, 2007 at 03:20:59PM +0100, Klaas-Jan Stol wrote:
> I've done some more work on the grammar of Pynie.
>
> This patch also includes the other patch I sent yesterday (so that one
> can be skipped).
Applied, thanks. I'll be making some cleanups momentarily.
> This grammar is ALMOST
hi,
attached a patch that adds the last few bits of the Python grammar.
Please note that there may be bugs, but I put in all rules, (not using
the optable, that one is commented out)
I had to put some things into comments in the ASTgrammar, the expression
stuff needs work.
I removed the lef
hi,
attached is Grammar.pg for Pynie. It's complete, but it needs some
rework: the optable needs to be welded in again, instead of rec.decent
rules for parsing expressions. This mail is just for archiving purposes
(or in case someone feels brave). I'll have a look at putting back the
optable
Am Sonntag, 25. Februar 2007 12:28 schrieb Klaas-Jan Stol:
> Can you tell whether pbc_output_is() can take PIR code and compile it
> during running the test? Or does is always expect the pbc file to be
> present?
As said, it doesn't make sense to feed .pir code into these tests. So no /
yes.
leo
On 2/26/07, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Am Sonntag, 25. Februar 2007 12:28 schrieb Klaas-Jan Stol:
> Can you tell whether pbc_output_is() can take PIR code and compile it
> during running the test? Or does is always expect the pbc file to be
> present?
As said, it doesn't make sen
On Mon, Feb 26, 2007 at 09:24:29AM -0600, Patrick R. Michaud wrote:
: On Mon, Feb 26, 2007 at 07:09:58AM -0800, Jerry Gay wrote:
: > # New Ticket Created by Jerry Gay
: > # Please include the string: [perl #41623]
: > # in the subject line of all future correspondence about this issue.
: > # ht
jerry gay wrote:
On 2/26/07, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Am Sonntag, 25. Februar 2007 12:28 schrieb Klaas-Jan Stol:
> Can you tell whether pbc_output_is() can take PIR code and compile it
> during running the test? Or does is always expect the pbc file to be
> present?
As said, i
On Fri Feb 23 14:46:17 2007, [EMAIL PROTECTED] wrote:
> hi,
>
> it might be a good idea to add a flag to parrot that checks at runtime
> whether any deprecated ops are used.
> the flag should be turned off by default; some ops like find_global are
> used all over the place, so if it would be
> t
# New Ticket Created by "Alek Storm"
# Please include the string: [perl #41619]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41619 >
This patch adds the add_attr, rem_attr, and rem_attr_str vtable
methods. These will com
It is rather annoying that attributes don't JFW everywhere, yes. I do
wish, in general, that ParrotClass and PMC had more in common.
I'm not sure how I'm to access these via PIR: I get the same
src/objects.c:1452: failed assertion `(class)->pmc_ext'
error after applying this patch.
I'm going
# New Ticket Created by "Alek Storm"
# Please include the string: [perl #41620]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41620 >
This patch changes the , , and syntax in opcodes to , , and , respectively. The argume
18 matches
Mail list logo
