[Top][All Lists]

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

[Octave-bug-tracker] [bug #41305] generate human-readable error strings

From: Max G.
Subject: [Octave-bug-tracker] [bug #41305] generate human-readable error strings from arpack error codes
Date: Mon, 27 Jan 2014 19:01:17 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/31.0.1650.63 Chrome/31.0.1650.63 Safari/537.36

Follow-up Comment #16, bug #41305 (project octave):

I'm very sorry, but I totally disagree with all renaming, assigning as feature
request and the pursued solution.

There are cases, where  eigs(M,1,'LM')  fails, but
 eigs(M,6,'LM')  successfully returns.
Also, failure seem to be version dependend, as comment 2 states.

That cannot be handled by extended error messages, albeit they were great.
That is a plain inconsistent behaviour, that has to be fixed!


Reply to this item at:


  Nachricht gesendet von/durch Savannah

reply via email to

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