Re: [perl #39313] [TODO] or [BUG] improve PMC compiler

2008-09-16 Thread Allison Randal
Klaas-Jan Stol wrote: This ticket doesn't seem to be closeable as is.Would it be good enough if pmc2c.pl spit out an error on the above definition, or is this even something that pmc2c.pl should be concerned about? The goal of the ticket should be for pmc2c.pl to entirely parse the input PMC

[perl #39313] [TODO] or [BUG] improve PMC compiler

2008-09-05 Thread Christoph Otto via RT
On Fri Jun 27 13:14:53 2008, coke wrote: While I think this particular example is now valid with the new calling conventions, you can get a similar effect with: METHOD BORK BORK parent() { /* nothing to see here*/ } This ticket doesn't seem to be closeable as is. Would it be good

Re: [perl #39313] [TODO] or [BUG] improve PMC compiler

2008-09-05 Thread Will Coleda
On Fri, Sep 5, 2008 at 3:45 AM, Christoph Otto via RT [EMAIL PROTECTED] wrote: On Fri Jun 27 13:14:53 2008, coke wrote: While I think this particular example is now valid with the new calling conventions, you can get a similar effect with: METHOD BORK BORK parent() { /* nothing to see

Re: [perl #39313] [TODO] or [BUG] improve PMC compiler

2008-09-05 Thread Klaas-Jan Stol
On Fri, Sep 5, 2008 at 1:28 PM, Will Coleda [EMAIL PROTECTED] wrote: On Fri, Sep 5, 2008 at 3:45 AM, Christoph Otto via RT [EMAIL PROTECTED] wrote: On Fri Jun 27 13:14:53 2008, coke wrote: While I think this particular example is now valid with the new calling conventions, you can get a

Re: [perl #39313] [TODO] or [BUG] improve PMC compiler

2008-09-05 Thread Will Coleda
On Fri, Sep 5, 2008 at 9:07 AM, Klaas-Jan Stol [EMAIL PROTECTED] wrote: On Fri, Sep 5, 2008 at 1:28 PM, Will Coleda [EMAIL PROTECTED] wrote: On Fri, Sep 5, 2008 at 3:45 AM, Christoph Otto via RT [EMAIL PROTECTED] wrote: On Fri Jun 27 13:14:53 2008, coke wrote: While I think this

[perl #39313] [TODO] or [BUG] improve PMC compiler

2008-06-27 Thread Will Coleda via RT
On Tue Jun 06 07:40:55 2006, leo wrote: It's easy to add 'invalide' code to .pmc files. E.g. I had defined: METHOD parent() { return PMC_pmc_val(SELF) ? PMC_pmc_val(SELF) : PMCNULL; } Due to the absence of a return value, the PMC compiler just ignores this 'method'

[perl #39313] [TODO] or [BUG] improve PMC compiler

2008-05-17 Thread Patrick R. Michaud via RT
No action has occurred on this ticket since 2006, and I suspect it's obsoleted by improvements to PCCMETHOD and pmc2c anyway. I vote to close the ticket. Pm

Re: [perl #39313] [TODO] or [BUG] improve PMC compiler

2006-06-08 Thread Joshua Juran
On Jun 7, 2006, at 8:08 AM, Klaas-Jan Stol wrote: I had a look at this, but I'm not that good at Perl, and regular expressions. However, I found where things go wrong, so someone who really groks REs may fix it. I'm no Abigail, :-) but I'll try to help. THe problem is (well, at least I

Re: [perl #39313] [TODO] or [BUG] improve PMC compiler

2006-06-07 Thread Klaas-Jan Stol
Hi, I had a look at this, but I'm not that good at Perl, and regular expressions. However, I found where things go wrong, so someone who really groks REs may fix it. THe problem is (well, at least I think it is) at about line 440 in pmc2c.pl sub parse_pmc { my $code = shift; my

[perl #39313] [TODO] or [BUG] improve PMC compiler

2006-06-06 Thread via RT
# New Ticket Created by Leopold Toetsch # Please include the string: [perl #39313] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/rt3/Ticket/Display.html?id=39313 It's easy to add 'invalide' code to .pmc files. E.g. I had defined: METHOD