|
From: | Tatsuro MATSUOKA |
Subject: | [Octave-bug-tracker] [bug #47820] Uncomprehesive behaviors for functions that are not recognized in configure |
Date: | Mon, 02 May 2016 05:39:36 +0000 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36 |
Follow-up Comment #2, bug #47820 (project octave): > Is the problem here that the documentation doesn't match the actual functionality, or is it just that you want the missing functionality to be implemented? No it is not. This is an issue representation of unsupported functions which comes from environments (intentional nor un-intentional). Current representation causes misleading like me. Perhaps other people feel in the same matter. Therefore I request the improvements way of representation for unsupported functions that were marked as "undefined" during configure. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?47820> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |