|
From: | Guillaume |
Subject: | [Octave-bug-tracker] [bug #50716] Undefined input to a classdef method |
Date: | Wed, 5 Apr 2017 11:07:34 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 |
Follow-up Comment #5, bug #50716 (project octave): Thanks for the explanation and the changeset. It solves the issues I was reporting. I understand all problems are not solved as shown in some of your tests: val = foo{end}.methodA (str(1:end)); Given that "end" always applies to the enclosing variable, "str" here, it is not entirely clear to me what the ambiguity is. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?50716> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |