At 09:51 AM 9/29/2001 -0400, Michael Maraist wrote:
> >
> > I generally divide signals into two groups:
> >
> > *) Messages from outside (i.e. SIGHUP)
> > *) Indicators of Horrific Failure (i.e. SIGBUS)
> >
> > Generally speaking, parrot should probably just up and die for the first
> > type,
Ask has found us a spot for the paper Alan was speaking of.
http://dev.perl.org/perl6/talks/
http://www.parrotcode.org/talks/
It's pretty interesting on first skim.
Dan
--"it's like this"---
Dan Sugals
It seems odd to have the chopn_s_ic and not a chopn_s_i op, this
patch adds this, and simillar ops (+ tests!) for shr and shl.
I don't know if these count as new features or not...
Also, string_chopn was not checking for OOB values for n, this is fixed
and the (currenlty skipped) jump test in basi
>
> I generally divide signals into two groups:
>
> *) Messages from outside (i.e. SIGHUP)
> *) Indicators of Horrific Failure (i.e. SIGBUS)
>
> Generally speaking, parrot should probably just up and die for the first
> type, and turn the second into events.
I don't know. SIGHUP is useful to
> > or have entered a muteX,
>
> If they're holding a mutex over a function call without a
> _really_ good reason, it's their own fault.
General perl6 code is not going to be able to prevent someone from
calling code that in-tern calls XS-code. Heck, most of what you do in
perl involves some sor
Ok, I've added (NV) to all of the integer trans ops arguments. See if that
helps.
-Original Message-
From: Michael G Schwern
To: Buggs
Cc: Gibbs Tanton - tgibbs; '[EMAIL PROTECTED] '
Sent: 9/28/2001 10:39 PM
Subject: Re: Solaris problems with trans.t
On Sat, Sep 29, 2001 at 05:22:41AM
