Re: Carp -- shortmess and longmess
From: Haakon Riiser (hakonrk_at_fys.uio.no)
Date: 07/26/04
- Next message: PhishR: "SNMP Set Request"
- Previous message: Michael Ragsdale: "Net::SFTP port problem"
- In reply to: Anno Siegel: "Re: Carp -- shortmess and longmess"
- Next in thread: Abigail: "Re: Carp -- shortmess and longmess"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 26 Jul 2004 19:45:27 +0000 (UTC)
[Anno Siegel]
> Carp tries to find a location on the call stack where it believes
> the error was introduced. When it can't find one, it switches to
> a full backtrace on its own accord. This seems to be happening here.
>
> The error location is always a point where a call crosses module
> boundaries. Give it such a call, and the results will be more
> consistent:
> [...]
Thanks; in the future, I should probably read beyond the first
paragraph before I consider filing bug reports. I thought the
summary was so clear, that I didn't bother to look to the second
paragraph, which begins: "Here is a more complete description of
how shortmess works." Embarrassing! :-)
-- Haakon
- Next message: PhishR: "SNMP Set Request"
- Previous message: Michael Ragsdale: "Net::SFTP port problem"
- In reply to: Anno Siegel: "Re: Carp -- shortmess and longmess"
- Next in thread: Abigail: "Re: Carp -- shortmess and longmess"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|