On Wed, Nov 19, 2003 at 11:49:14AM -0500, Dan Sugalski wrote: > > I think I'll take steps to make this less likely for Parrot, though I'm > not sure there's truly any good way to get around it anywhere but in the > actual application code.
This issue has come on p5p before (a few years ago) and the consensus, as I recall, was that $! shouldn't be tied directy to errno but should be set explicitly by the internals whenever a pp op was about to report an error to the application code. Tim.