[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #45444] Private functions inside namespace and
From: |
Amro |
Subject: |
[Octave-bug-tracker] [bug #45444] Private functions inside namespace and class directories |
Date: |
Fri, 30 Jun 2017 04:45:21 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0 |
Follow-up Comment #10, bug #45444 (project octave):
Don't know, I haven't had that problem in 4.2.1, it may be a regression in
dev.
First I would verify it's indeed about "varargin". Based on the error you've
shown in comment#7, I'm not so sure. Even if somehow "varargin" became empty,
the call should still go through, and not give a mysterious "out of bound"
error:
ret = myclass.static_function(varargin{:})
% if varargin is empty, the comma-separated list expands to empty, equivalent
to:
ret = myclass.static_function()
I think it has to do with the "myclass.static_function()" call itself, somehow
not parsing correctly?
I have seen something similar with regards to "obj.method()" vs. "method(obj)"
on regular class methods (which I previously mentioned in comment#5)..
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?45444>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/