octave-maintainers
[Top][All Lists]
Advanced

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

Re: Criteria for identifying must-fix bugs


From: Michael D. Godfrey
Subject: Re: Criteria for identifying must-fix bugs
Date: Wed, 09 Oct 2013 17:27:06 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130923 Thunderbird/17.0.9

On 10/09/2013 01:47 PM, Rik wrote:
Additional items we might want to consider are Item Group == Crash, since
even with bad input the interpreter should never segfault.  But there are
29 items with this property so this may be too many to fix and still
release Octave within a reasonable time frame.
I agree that, if at all possible, all known seg-faults should be fixed.
But, some users use the word "crash" more loosely, i.e Octave kept
running, but the expected result was not obtained.  Are there really
29 separate seg-faults?  UGH!

Also, I did not see the parser error that you mentioned.  But, there
are:

#35535: Index-_expression_ parsing issue


#34444: <TAB> complete does not work after transpose operator and math operator


#33304: power operator precedence and direction

   This is still open, but may not be blocking.



Michael


reply via email to

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