[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dynamic linking of .oct files and symbol names in libcruft (intrp.f
From: |
John W. Eaton |
Subject: |
Re: Dynamic linking of .oct files and symbol names in libcruft (intrp.f in libcruft/villad) |
Date: |
Tue, 9 Sep 2003 15:35:39 -0500 |
On 9-Sep-2003, withaar <address@hidden> wrote:
| If you are using c++, you could include the file with namespace scope
| around it:
|
| namespace mylib {
|
| #include "mylib.h"
|
| }
|
| which should solve name conflicts.
If the "foreign" intrp function were in C++, then the name would be
mangled and the linker wouldn't see the conflict with Octave's intrp
function which is Fortran.
jwe
-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.
Octave's home on the web: http://www.octave.org
How to fund new projects: http://www.octave.org/funding.html
Subscription information: http://www.octave.org/archive.html
-------------------------------------------------------------