In article <v04011703b2b085822164@[207.135.77.148]>, Vicki Brown <vlb@cfcl.com> writes: > At 11:39 -0800 12/30/98, John W Baxter wrote: >> I can't imagine running a development tool under MPW without that >> behavior...it's what every compiler, etc, has done under MPW since >> 1986. Since MPW installs itself as a "foreign file system" <it was > MPW tool output does tend toward this standard and that's what the Mac is > all about: standards. > So maybe the behaviour could be "standard Perlish" for the standalone > MacPerl and use the > # Warning: something's wrong, <> chunk 1. > File ':test.pl'; Line 1 > # Died. > File ':test.pl'; Line 1 > format under MPW? Sounds like more headaches for the portability minded, instead of fewer. > Questions: If the output format changes to match "standard" Perl format for > the standalone MacPerl app, > 1) how does this affect the Jump To: menu item in MacPerl? This could easily be changed. I'm not even sure whether Jump To is not in fact already capable of handling either message style. > 2) How would this affect the BBEdit error Browser interaction? No idea. Matthias -- Matthias Neeracher <neeri@iis.ee.ethz.ch> http://www.iis.ee.ethz.ch/~neeri "Those would be ad hominem attacks if Perl were a hominid." -- Tom Christiansen ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch