Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> As the semantic of the clone-call is not clear yet can some-one please
> apply this patch
Done, thanks.
> bye
> boe
leo
Index: t/pmc/io.t
===
RCS file: /cvs/public/parrot/t/pmc/io.t,v
retrieving revision 1.5
diff -u -r1.5 io.t
--- t/pmc/io.t 9 Jul 2003 19:27:05 - 1.5
+++ t/pmc/io.t 28 Jul 2003 17:39:02 -
@@ -100,6 +100,8 @@
ok 6
OUTPUT
+SKIP
d layer is in the stack or not.
-Melvin
Jos Visser <[EMAIL PROTECTED]>
07/28/2003 10:38 AM
To: Juergen Boemmels <[EMAIL PROTECTED]>
cc: Perl6 Internals <[EMAIL PROTECTED]>
Subject: Re: [RfC] Semantics of clone for PIO-objects.
O
On Mon, Jul 28, 2003 at 03:30:46PM +0200 it came to pass that Juergen Boemmels wrote:
> Comments
My first hunch is to see the ParrotIO object as a channel of data into
an underlying file (leaving "channel", "data", and "file" vaguely
defined for now)... This would mean that every ParrotIO object h
Hello,
On some systems t/pmc/io_6.pasm fails because of a double free. The
problem is that the clone call adds a reference to ParrotIO object,
but the ParrotIO object is neither garbage collected nor refcounted so
it gets destroyed when its first refrence is destroyed.
The solution of that memory
