Re: feval call to a subfunction fails when it is in a subfunction

[Sidney Markowitz]

Jaroslav Hajek wrote, On 2/10/09 8:36 AM:
> The rather general fix for development sources was not transplantable
> to 3.2.3 due to the binary compatibility policy. A separate fix needs
> to be created.

So this is a known bug in the 3.2.3 branch? Which bug # is it? I didn't 
find it (or didn't notice it) searching for problems with feval. Is the 
problem with feval just one symptom of something more general?

Is this considered serious enough to port to the 3.2.x branch? I don't 
have much experience with Octave yet, but this completely breaks mgene, 
a large gene prediction package that was my reason for trying to get 
Octave to work, and it does look like this use of feval would be quite 
common.