|
From: | Muhali |
Subject: | [Octave-bug-tracker] [bug #36375] path order after path(p) |
Date: | Wed, 09 May 2012 16:49:21 +0000 |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 |
Follow-up Comment #6, bug #36375 (project octave): The behavior of path(p) of putting everything on top successively is not intuitive to me; it would be intuitive for addpath(p) though. ML behaves as mentioned: path(p) assigns p to the full path sequence, which also means that it becomes non-functional if p is bad. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?36375> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |