Should crash be the top of ex.err?

new topic     » topic index » view thread      » older message » newer message

One thing I've noticed is that calling crash() causes crash() to be at the head of the ex.err file.

While I understand why this is the case, I suggest that the error should be associated with where the error was thrown, not with the crash() routine.

Although it's technically part of the stack trace, it's not really part of the crash at all.

The exception (of course) is if there is an actual error in crash().

From my lazy developer's perspective, instead of:

C:\Euphoria\include\std\error.e:50 in procedure crash()  
Unable to find parameter in queue pitch for position 50400  
    fmt = {85'U',110'n',97'a',98'b',108'l',101'e',32' ',116't',111'o',32' ', 
102'f',105'i',110'n',100'd',32' ',112'p',97'a',114'r',97'a',109'm',101'e', 
116't',101'e',114'r',32' ',105'i',110'n',32' ',113'q',117'u',101'e',117'u', 
101'e',32' ',37'%',115's',32' ',102'f',111'o',114'r',32' ',112'p',111'o', 
115's',105'i',116't',105'i',111'o',110'n',32' ',37'%',100'd'} 
    data = { 
             {112'p',105'i',116't',99'c',104'h'}, 
             50400 
           } 
    msg = {85'U',110'n',97'a',98'b',108'l',101'e',32' ',116't',111'o',32' ', 
102'f',105'i',110'n',100'd',32' ',112'p',97'a',114'r',97'a',109'm',101'e', 
116't',101'e',114'r',32' ',105'i',110'n',32' ',113'q',117'u',101'e',117'u', 
101'e',32' ',112'p',105'i',116't',99'c',104'h',32' ',102'f',111'o',114'r', 
32' ',112'p',111'o',115's',105'i',116't',105'i',111'o',110'n',32' ',53'5', 
48'0',52'4',48'0',48'0'} 
 
... called from [MY_PATH]\parameter_queue.e:77 in function get_value()   
    this = { 
             {112'p',105'i',116't',99'c',104'h'}, 
             { 
               {0,1259,0,110'n',7,1259,0}, 
               {1260,5039,110'n',110'n',1,3779,0}, 
               {5040,6299,110'n',110'n',7,1259,0}, 
               {6300,10079,110'n',110'n',1,3779,0}, 
               {10080,11339,110'n',110'n',7,1259,0}, 
               {11340,15119,110'n',110'n',1,3779,0}, 
               {15120,16379,110'n',110'n',7,1259,0}, 
    ... 
I really just want to see something more like:
crash() called from [MY_PATH]\parameter_queue.e:77 in function get_value() 
Unable to find parameter in queue pitch for position 50400  
    this = { 
             {112'p',105'i',116't',99'c',104'h'}, 
             { 
               {0,1259,0,110'n',7,1259,0}, 
               {1260,5039,110'n',110'n',1,3779,0}, 
               {5040,6299,110'n',110'n',7,1259,0}, 
               {6300,10079,110'n',110'n',1,3779,0}, 
               {10080,11339,110'n',110'n',7,1259,0}, 
               {11340,15119,110'n',110'n',1,3779,0}, 
               {15120,16379,110'n',110'n',7,1259,0}, 
    ... 

This will be helpful not just for me, but for the editor (like wee) which is trying to point me to an error, but instead ends pointing to the wrong thing through no fault of its own.

- David

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu