Re: What to do with builtin functions not in libinterp subdirectory

[John W. Eaton]

I'm attaching something you can play with if you like.

I kept the Ffoo function definition.  I don't see that it helps to have 
these built-in functions defined as member functions of a class.  I 
think it is convenient that we can call them using Ffoo anywhere in 
Octave now.  That's another thing you'll need to address, which is how 
to generate the list of declarations that is currently stored in 
builtin-defun-decls.h.

Anyway, this code crashes Octave on startup for me because place where 
these function pointers are stored is symbol_table::fcn_table, and that 
is a static object which apparently for me is not initialized ahead of 
the first call to the builtin_function_installer constructor.

One solution would be to use a singleton object for fcn_table instead of 
a static data member.  That would not be too hard to do, I suppose.

jwe

diffs.txt
Description: Text document