On 7/15/99 at 3:51 PM, Vicki Brown <vlb@cfcl.com> wrote: > At 09:11 -0700 7/15/99, Brian McNett wrote: > > > > All *I* can do is agree that it's weird! Also not particularly > > helpful in the second case! Is this JUST MacPerl, or do other Perls > > do this too? > > It appears to be a MacPerl/BBEdit interaction glitch. Unix Perl > doesn't change and MacPerl app doesn't either so I've filed a bug > report at BB. That comment causes MacPerl to generate a funny multi-line error. BBEdit is stuck parsing STDERR into an error browser, and you can presumably print anything to STDERR as well to confuse it, so it isn't a trivial process. What it does is it first runs a quick heuristic on the text to figure out how many errors there are. If it for some reason can't parse the errors, or doesn't parse out as many as the guess, it will dump STDERR to the output window so that you don't loose information. If you have errors that aren't being parsed out correctly send a bug report (as was done in this case) to support@barebones.com so we can have a look at it. Life would be much simpler if errors were passed back in a record in the apple event in addition to the STDERR chunk. Maybe in the future when Matthias has more time than he knows what to do with I can convince him to implement this :-) Jim -- Jim Correia Bare Bones Software, Inc. correia@barebones.com <http://web.barebones.com> ===== Want to unsubscribe from this list? ===== Send mail with body "unsubscribe" to macperl-request@macperl.org