Chris Nandor <pudge@pobox.com> writes: >I disagree. If this behavior is to be kept, I think it should be limited >to output directed to an MPW window itself, if possible. There are too >many places in modules and programs, including core modules that come with >Perl, that depend on a certain format. Could the MPW style formatting of the error message be done after the warn() or die() trickles up through the eval stack? If it comes down to loosing the MPW style errors or cross platform incompatibility, I'd rather keep things so they work right in MPW. (I use some tools that are direct ports of command line utilities on other platforms, and I hate the fact that they don't send messages that can be evaluated directly by MPW. I'm getting to the point where I want to write wrappers around them that reformat their diagnostics. >If you want to take it on yourself to notify every author of every module >on CPAN that checks $SIG{__WARN__}, $SIG{__DIE__}, $@, etc., then I suppose >that would be a reasonable alternative, too. Well, since so many of them are causing damage already (as described in the perl5porters thread on $SIG{__DIE__} a few weeks back) it might be a good idea for all of them to be checking their code anyway. And since they're mucking with it anyway... Actually, I can imagine lots of Mac-bigots being less than thrilled to special case Mac-mangled die messages. -- Andrew Langmead ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch