On Mon, Jul 18, 2011 at 10:41:30AM -0400, Peter Lobsinger wrote:
> On Sun, Jul 17, 2011 at 11:00 AM, Patrick R. Michaud <pmich...@pobox.com> 
> wrote:
> > On Sun, Jul 17, 2011 at 10:21:19AM +0200, Moritz Lenz wrote:
> >>
> >> Question to the Parrot developers: How could I implement DESTROY methods
> >> in Rakudo? Is there any vtable I can override, or so? Note that such a
> >> method might itself allocate new GCables. While not urgent, it's
> >> important for us in the long run.
> >
> > A possibly related (and more relevant) question for Parrot devs:
> > is there any reason that FileHandle PMCs do not automatically
> > flush + close on destruction?
> The destructor does exactly that, but is not triggered by global teardown.

To be a bit more direct, then:  Several of Parrot's target languages 
have the semantic that normal program exit will cause any open 
filehandles to be flushed and closed automatically.  How does a HLL
writer achieve this in Parrot?


Reply via email to