octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #50359] clearer documentation for difference b


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #50359] clearer documentation for difference between isnull and isempty
Date: Thu, 14 Sep 2017 14:55:06 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Follow-up Comment #22, bug #50359 (project octave):

Kai - for a practical example, it would be nice if something like
containers.Map allowed deleting a key-value pair like this


map = containers.Map ({"one", "two"}, {1, 2});
map("two") = [];


This kind of indexing would normally delete the element of map that the index
"two" references, but in this case it just assigns it a value of an empty
array.

I don't know which behavior is compatible, I'm just giving an example where
assigning to a null array can't be done by simply forwarding the assignment to
an array that is stored in the object. Not all objects are wrappers around a
matrix so the transitive assignment would work.

Here is a practical example from the symbolic package:


x = sym ("x", [10, 1]);
x(3) = [];


This does work, but only because it also works with zeros(0,0) or any empty
array acting as a signal for deletion.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50359>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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