bugGNU Octave - Bugs: bug #56213, Octave warning/error IDs should...

 
 

bug #56213: Octave warning/error IDs should all be in the "Octave:" namespace

Submitter:  Rik <rik5>
Submitted:  Thu 25 Apr 2019 04:28:08 AM UTC
   
 
Category:  Octave Function Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Feature Request
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 25 Apr 2019 03:53:48 PM UTC, comment #2: 

I put all the warning/error IDs I could find with grep in to the Octave namespace (https://hg.savannah.gnu.org/hgweb/octave/rev/0a62d9a6aa2d).

I'm marking the bug as fixed, but we can leave it open if you want to add some documentation about when to use the Octave namespace.  Or you can close this and file a new documentation bug report.

Rik <rik5>
Group administrator
Thu 25 Apr 2019 05:59:34 AM UTC, comment #1: 

We might also document that the "Octave:" warning prefix is reserved for use by Octave, and packages and user code should avoid using it as a prefix for their own warning IDs.

Mike Miller <mtmiller>
Group Member
Thu 25 Apr 2019 04:28:08 AM UTC, original submission:  

Many, dare I say most, warning/error IDs are not located within the Octave namespace.  Fixing this would be more Matlab compatible which always puts its errors within the MATLAB namespace.  And it would more clearly distinguish Octave's errors from user-written error IDs.

Rik <rik5>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-05-07 rik5 Open/ClosedOpen Closed
    2019-04-25 rik5 StatusConfirmed Fixed

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code