Skip to Content.
Sympa Menu

h5part - [H5part] Re: notes on changes to the H5hut trunk

h5part AT lists.psi.ch

Subject: H5Part development and discussion

List archive

[H5part] Re: notes on changes to the H5hut trunk


Chronological Thread 
  • From: Achim Gsell <achim AT cybercity.ch>
  • To: Mark Howison <MHowison AT lbl.gov>
  • Cc: h5part AT lists.psi.ch
  • Subject: [H5part] Re: notes on changes to the H5hut trunk
  • Date: Thu, 1 Jul 2010 14:53:05 +0200
  • List-archive: <https://lists.web.psi.ch/pipermail/h5part/>
  • List-id: H5Part development and discussion <h5part.lists.psi.ch>

On Jun 30, 2010, at 9:57 PM, Mark Howison wrote:

> Hi Achim,
>
> Is it just an issue between C and C++?

No, it is not just an issue between C and C++ (by the way: the C++ issue can
be solved with namespaces, as Benedikt already mentioned). But it is a
potential issue with any new bindings for whatever language.

> Because the current build
> system we have in the 1.6 branch creates the Fortran library by mixing
> the Fortran bindings in with the C bindings, so they seem to be able
> to coexist. Or is the issue with linking external code against the
> library? For instance, if I tried to link a C H5Part program against
> the Fortran library, would it break?

No, it wouldn't break.

But let's have a look on other projects. How do they handle this issue?

hdf5-1.8.5: core library plus libraries for the language bindings.
mpich2-1.2.1p1: core library plus libraries for the language bindings
openmpi-1.4.2: ore library plus libraries for the language bindings
ImageMagick: core library plus libraries for the language bindings

Actually I don't know any project handling this in another way. Keep it
simple also means: do it the usual way ...

Achim






Archive powered by MHonArc 2.6.19.

Top of Page