[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57082] [io] Inconsistent use of "<fcn_name>:

From: Andrew Janke
Subject: [Octave-bug-tracker] [bug #57082] [io] Inconsistent use of "<fcn_name>: " prefix in error and warning messages
Date: Sat, 19 Oct 2019 00:34:25 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:69.0) Gecko/20100101 Firefox/69.0


                 Summary: [io] Inconsistent use of "<fcn_name>: " prefix in
error and warning messages
                 Project: GNU Octave
            Submitted by: apjanke
            Submitted on: Sat 19 Oct 2019 12:34:23 AM EDT
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: other
        Operating System: Any



The io Octave Forge package, as of 2.4.13, does the standard Octave thing of
prefixing its error and (some) warning messages with "<fcn>: ", indicating
which function raised the error. However:

* Not all occurrences of error(...) use this prefix.
* In some, the prefix includes the ".m" for the function M-file name; I don't
think that's standard
* In a couple places, it uses the wrong function name.

The attached patch cleans this up, making the error messages more consistent.


File Attachments:

Date: Sat 19 Oct 2019 12:34:23 AM EDT  Name:
octave-io-consistent-fcn-name-prefix-in-error-messages.patch  Size: 25KiB  
By: apjanke



Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]