[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Should library error() calls have newlines?
|
From: |
Andrew Janke |
|
Subject: |
Re: Should library error() calls have newlines? |
|
Date: |
Sun, 5 May 2019 13:15:23 -0400 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 |
On 5/5/19 12:18 PM, Carnë Draug wrote:
> On Thu, 2 May 2019 at 23:14, Andrew Janke <address@hidden> wrote:
>>
>> Hi, Octave maintainers,
>>
>> Question about best practice for Octave package development: Should the
>> error() calls raised in package library functions end in newlines, so
>> the stack traces are suppressed, or not, so stack traces are displayed?
>> Trailing newline in error message strings controls stack trace display,
>> right?
>
> Hi
>
> Yes, a trailing newline will hide the stack trace.
>
> I don't think there's any official stance on this though, but I would
> say it's better to not hide it. Let the whole stack trace be
> displayed since hiding it makes debugging more difficult.
>
Okay. I'll leave the stack traces displayed in my library code.
Thanks!
Cheers,
Andrew