Vladimir Lipsky <[EMAIL PROTECTED]> wrote:
> Parrot_loadbc(interpreter, pf);
> Did you catch the difference between the 2nd actual parameter and
> the function name? Maybe it's worth renaming? E.g. Parrot_loadpf()
Sounds reasonable. Or Parrot_set_pf().
> 0x4C56
leo
Michal Wallace <[EMAIL PROTECTED]> wrote:
> Is it possible to print out the line number
> of the bad instruction when parrot encounters
> an error and fails?
Yep. I'll have a look at it.
> I don't suppose there's one magic error routine
> that controls all the error messages, and someone
> could
Michal Wallace <[EMAIL PROTECTED]> wrote:
> Looking more at exceptions here... I
> used to be able to put arbitrary
> stuff in the _message slot of a
> ParrotException... Now we can only use
> strings. Is that permanent?
Depends on what exceptions finally are. But the standard entries like
"_mess
Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote:
> I think the 'imclexer.c' is generated from 'imcc.l' during maintainance. So
> I made the patch in both files.
Just for imcc.l is enough.
Thanks, applied.
leo
Michal Wallace <[EMAIL PROTECTED]> wrote:
> What is the _return_cc attribute on an
> exception? Can I use it to resume the
> code as if the exception never happened?
When an exception is resumable, you can return by invoking this return
continuation. But details (i.e. is C<_return_cc> put into P1
On Tuesday, December 2, 2003, at 11:49 , Melvin Smith wrote:
At 07:59 PM 12/2/2003 -0800, Steve Fink wrote:
Do you really want to generate the extra unused code at the end of all
the subroutines? I don't think you want to autodetect whether the code
is guaranteed to return.
Good point. Its easy
Sterling Hughes <[EMAIL PROTECTED]> wrote:
> Should PerlString support a get_pmc_keyed() method (according to Perl
> 5/6 semantics), or is this a point where its about time to start
> implementing our own PMCs?
get_pmc_keyed() seems a bit heavy to handle single chars in a
PerlString (Each char wo
Am 04.12.2003 um 15:17 schrieb Leopold Toetsch:
Sterling Hughes <[EMAIL PROTECTED]> wrote:
Should PerlString support a get_pmc_keyed() method (according to Perl
5/6 semantics), or is this a point where its about time to start
implementing our own PMCs?
get_pmc_keyed() seems a bit heavy to handle
Thies C . Arntzen <[EMAIL PROTECTED]> wrote:
> Am 04.12.2003 um 15:17 schrieb Leopold Toetsch:
>> Can you use native STRINGs for that?
> sure, if we only knew the type of the variable we're accessing:
> function dump0($a)
> {
> echo printf("%s\n",$a[0]);
> }
> dump0("hallo"); // called with a
On Dec 3, 2003, at 12:03 PM, Dan Sugalski wrote:
At 12:17 PM +0100 12/3/03, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> *) Exceptions we're happy with
Create an Exception class hierarchy?
I'm not 100% sure I want to go with a real OO style of exceptions, but
that might jus
On Dec 2, 2003, at 8:49 PM, Melvin Smith wrote:
At 07:59 PM 12/2/2003 -0800, Steve Fink wrote:
On Dec-02, Melvin Smith wrote:
Do you really want to generate the extra unused code at the end of all
the subroutines? I don't think you want to autodetect whether the code
is guaranteed to return.
Good
As discussed in the last IMCC RFC, I've committed a few of the changes.
IMCC will now generate an error if the register type is unknown
rather than just assign it a PMC register.
P reg types are pmc, object, or a valid classname. Use pmc or
object for "generic" P register to defer type checking.
I
12 matches
Mail list logo
