Re: Exposing internal functions

[Kai Torben Ohlhus]

On Mon, Sep 30, 2013 at 10:17 PM, Jose <address@hidden> wrote:

Hello.

I need to use one internal function from octave, specifically __fdjac__.

In order to do so I can:
1- Copy it from its original directory to anywhere in octave's path.
2- Create a symbolic link from anywhere in octave's path pointing to the real file.

Neither of the previous methods will survive a new octave installation in a new directory. I wonder if there is a better way to do it so that I don't have to care about doing this every time that I install a new version of octave, e.g. adding something to octaverc.

Br,
Jose
_______________________________________________
Help-octave mailing list
address@hidden
https://mailman.cae.wisc.edu/listinfo/help-octave

Hello Jose,

scripts/optimization/private/__fdjac__.m seems to be a finite difference jacobi operator used by the exposed functions scripts/optimization/fsolve.m and scripts/optimization/fminunc.m. As I don't know how you use that function, I cannot say if it makes sense to modify your program using the exposed functions.

__fdjac__.m only counts about 20 lines of m-code and there is no matching function in MATLAB AFAIK. So I think that m-file it is to trivial to be exposed. Maybe you can integrate the appropriate of the two for-loops (each 9 lines of code) into your program logic directly without cluttering your program?

Best,

Kai