From octave-maintainers-request at bevo dot che dot wisc dot edu Fri Jun 29 14:38:58 2001
Subject: Re: [patch] Use C linkage for dynamic linking
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
Cc: octave-maintainers at bevo dot che dot wisc dot edu
Date: Fri, 29 Jun 2001 14:38:52 -0500

On 29-Jun-2001, Mumit Khan <khan at NanoTech dot Wisc dot EDU> wrote:

| Now there's the issue of being able to load existing .oct files without
| having to rebuild everything. Now that Octave has decided to go the C
| linkage route, is it important to provide backward compatibility for 
| loading existing .oct files? If so, it could be done using a combination
| of the two approaches -- have the mangler return a *list* of possible 
| mangled names (eg., list containing a C linkage name and a C++ linkage 
| name that's appropriate for that ABI), and octave_shlib::search will 
| iterate over the list.  If this is appropriate, it's rather trivial to 
| work up a patch (take a bit longer if I have to use SLList<T> instead
| of std::list<T>). 

I don't see this as necessary, but when I install a new version of
Octave, I typically rebuild all .oct files that I am using with it.
Not everyone may not do that, however, so I'd like to know what other
people think.

Thanks,

jwe