|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #50359] clearer documentation for difference between isnull and isempty |
Date: | Thu, 23 Feb 2017 14:01:17 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 |
Follow-up Comment #9, bug #50359 (project octave): Ernst - the only reason for this difference to exist is because it must for Matlab compatibility. Matlab strictly differentiates between the two assignments jwe shows in comment #7, so Octave must as well. This is the entire reason for the existence of the null type and why it loses its type upon assignment to a variable. Once a null type is assigned, it is no longer null. The only utility of the null type is for this assignment syntax that allows elements of an array to be deleted. Thus the only use of the isnull function is probably in an overloaded class implementation of the subsasgn method. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?50359> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |