bugGNU Octave - Bugs: bug #47919, Error messages for mismatched...


bug #47919: Error messages for mismatched struct fields is not informative

Submitter:  Lachlan Andrew <lachlan>
Submitted:  Fri 13 May 2016 11:51:24 PM UTC
Category:  Interpreter Severity:  1 - Wish
Priority:  5 - Normal Item Group:  Feature Request
Status:  Patch Submitted Assigned to:  lachlan
Originator Name:  Lachlan Open/Closed:  * Open
Release:  * dev Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup

Wed 18 Jan 2017 11:38:49 PM UTC, comment #1: 

What is the test case that results in this error message?

John W. Eaton <jwe>
Group administrator
Fri 13 May 2016 11:51:24 PM UTC, original submission:  

I'm not sure if this is worth the complexity, but when I got the error "orderfields: structs must have same fields up to order", I thought that it may be useful to indicate which fields were different.

The patch is less trivial than I expected, and probably not worth the maintenance burden, but since I have written it, I'll post it here once I have the bug number.  Currently, if only one field is in one struct but not the other, it prints the name of that field; otherwise it prints the number of such fields.  There are many more verbose possibilities (like listing all shared/LHS-only/RHS-only fields if that number is below a threshold), and I'm happy to implement something different if people think it is worth it, but I'm afraid of the tail wagging the dog.

Lachlan Andrew <lachlan>


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

Attach Files:

Attached Files


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by lachlan (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 project members can vote.


    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-05-14 lachlan Attached File- Added bug_47919_field_mismatch.v1.cset, #37153
        StatusNone Patch Submitted
        Assigned toNone lachlan

    Back to the top

    Powered by Savane 3.12