Little problem with dynamic linked libraries

[John W. Eaton]

On 21-Jun-1999, Luigi Palopoli <address@hidden> wrote:

| Hello everybody!
| I have written a little C++ program for doing faster simulations.
| As shown in the manual, this procedure is exported to the simulation
| core 
| by using DEFUN_DLD. Now, I need to have, in the same program, another
| for configuring the internal parameters. This function should be
| exported too.
| The problem is that the octave interpreter only has knowledge of one
| procedure, the one named after the file name, seemingly. 
| The thing is rather strange, since the module lsode.cc and others like
| it, easily exports two or more functions which are imported into the
| octave environment.
| Has anyone suggestions?

Do the same thing Octave does.  Use multiple links in the filesystem.
If your foo.cc file includes functions foo and bar:

  mkoctfile foo.cc
  ln foo.oct bar.oct

jwe



---------------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.  To ensure
that development continues, see www.che.wisc.edu/octave/giftform.html
Instructions for unsubscribing: www.che.wisc.edu/octave/archive.html
---------------------------------------------------------------------