In article <[EMAIL PROTECTED]>, Robert Spier <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 23, 2004 at 06:00:06AM -0000, Dan Jacobson wrote: > > Today again lots of head scratching because bash and perl don't prefix > > their error messages with a "bash:" or a "perl:", so bash scripts with > > bits of perl often take deep scrutinization to figure out what the > > problem was. > That may well be the case, but Perl has done its error messages this way > for 16 years, and changing it now would boringly break lots of things. I took a whack at this FAQ, but then discovered while trying to write an example that all of the shells I tried on Mac OS X (bash, tcsh, sh) prefixed the errors with the shell name, even when called through system(). I got the same results on NetBSD and OpenBSD. The only way I could get a non-prefixed error was messing up the shebang line. #!/usr/bin/pearl print "Hello World\n"; And I then had to use perl to invoke that script. % perl script.pl Can't exec /usr/bin/pearl at script.pl line 1. Can anyone give me some situations or snippets of code and which systems have problems? If not, I do not have anyway to develop good examples, and I cannot write the answer. -- brian d foy, [EMAIL PROTECTED]
