You still get the memory savings applying the nested function outside the file. But you do not need to use feval. Simply pass the function handle, let’s say fh, and evaluate it in your other program: fh(arg1,arg2).

–Loren

Based on the discussions on nested functions on the Mathworks Blogs, I have rewritten my code to be ‘nested’ so as to avoid ‘Out of Memory’ problems when repeatedly passing large arrays to sub-functions.

These sub-functions were originally used by different parent functions, hence it would be convenient to maintain a single source code for them.

Do I achieve a similar benefit in terms of memory efficiency (avoid replication of memory space for large variables), if the nested sub-functions use “feval” to execute a code in a separate .m file? Is there any other solution ? (i am not sure i understand the matlab implementation of nesting properly).

Thanks

Vaclav

You might want to rearchitect your code so WrapperFun returns handles to the nested functions, perhaps in a struct or a cell array. Then use those handles.

–Loren

I have a somewhat different problem with nested function, I am not sure what the solution could be. I have about six structurally identical nested functions within a wrapper function that takes as an in input a string with a name of the nested function to call, for example

function u = WrapperFun(u,funname)
…
function u = A()
…
end %A
function u = B()
…
end %B
…
end %WrapperFun

where funname can be ‘A’ or ‘B’. I thought I can use feval(funname) to call the nested functions, but I am getting an error suggesting that feval cannot see the nested functions. Is there a different way to do this?

Thank you

I recommend you read the documentation on using global variables to understand how to access them. In each workspace that you want to see a particular global variable, you must declare that before making reference to it. This includes functions and the base workspace.

Furthermore, when I am inside a function into i cannot access global variables defined in the main workspace, with the exception of nested global variables, for exemple somthing like that:
function param=opt(goal)
global G
G=goal;
…..
param = lsqnonlin(@circuit,Z0,LB,HB,cond);
function F = circuit(Z)
%acces global
end
end