Bob Rogers <[EMAIL PROTECTED]> wrote:
>From: Leopold Toetsch <[EMAIL PROTECTED]>
>But it isn't known, if the last reference to that PMC is reused or not.
>If it is the last reference then the finalizer has to run, else not.
>As we don't have reference counts, an assign to an object
[Chip == [EMAIL PROTECTED] on Wed, 6 Apr 2005 18:24:49 -0400]
Chip> * On the third to last day of the month, someone (me, by
Chip> default) will create a release document...
Chip> * Starting on the first of the month, there will be a code
Chip> freeze...
Is it on?
Chip> No changes sho
Now, I think my patch is consistent.
internal_exception and real_exception have the same problem, both write in
stderr.
internal_exception directly, real_exception via find_exception_handler.
In both case, I add a fflush(stderr) after fprintf(stderr, ...).
Francois Perrrad
debuginfo.patch
Descri
William Coleda <[EMAIL PROTECTED]> wrote:
> The garbage collection issues that were stopping ParTcl's test suite
> (FYI, *not* Tcl's test suite) from working seem to be gone now!
I'm sorry to say that, but no GC bugs have gone, nor have any more been
fixed. As a DOD run isn't triggered at a repro
Hello!
The last weeks i've been in joy to implement a small vm for a
special runtime enviroment. As i'm a regular reader of the perl.perl6.*
mailing lists and know about parrot. I wondered how easy it would be
to throw away my own vm solution and use parrot.
There are currently only two things th
# New Ticket Created by Nick Glencross
# Please include the string: [perl #35116]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35116 >
This patch fixes a segfault in r7928 when load_bytecode cannot find the
pbc file. e.
On Tue, 2005-04-26 at 11:55 -0700, Nick Glencross wrote:
> This patch fixes a segfault in r7928 when load_bytecode cannot find the
> pbc file. e.g.
>
> .sub test
> # (Assumes hello.pbc doesn't exist)
> load_bytecode "hello.pbc"
> end
> .end
Looks good to me.
Before I apply it, I
On Tuesday 26 April 2005 23:41, chromatic wrote:
> Looks good to me. Â
To me too, except...
> Before I apply it, I think it needs a test case. ÂI'll write it from
> this example. ÂHow about t/stress/internal_exceptions.t?
>
> Any other feedback?
This should be a real_exception, not an internal one