Re: 3.2.1 release candidate 4

To put it more succinctly, we would all love to have this feature in octave, but nobody has had time to do it yet.

All of us are involved because we see something that we would like octave to have.  Some (like Jaroslav) are consistent and major contributors, and some (like myself) just do what we can, but all of us want to improve octave.

So jump in!  Open source software works because folks like us contribute.

Bob


Jaroslav Hajek wrote:

On Thu, Jul 2, 2009 at 4:59 PM, WMennerichW.Mennerich@... wrote:
  

Would it be possible to include a bugfix for this topic:
http://www.nabble.com/Error-with-function-handles-of-object-methods-to24185732.html
?
    

First of all, it is obviously only possible to apply patches that
exist, and I'm not aware of any. Second, I think this is more of a
missing feature than a bug. I intend to address this eventually and
already have an (hopefully) elegant idea how to do it, but I'm not
sure this will go into 3.2.x at all. Surely not 3.2.1, which is just
behind the door.

  

Without that working function handles, a lot of usefull stuff will not work.
E.g., if you have a cell array of ojects, you can use the cellfun function
to let all objects do a certain operation.
    

A possible workaround is to use @(varargin) method(varargin{:}) rather
than @method. This is less efficient and less readable, but at least
working.

  

I'm working in mobile comunications and my objects are mobilestations,
basestations, etc.
Together with parcellfun() from Octaveforcge there are powerfull options
available, but only with function handles of object methods which gives only
an error in octave v3.2 .

W.
    

If you really miss a particular feature, your most straightforward options are:
1. implement it yourself
2. make a donation for someone to do it for you and make it a priority
3. just wait

regards