Browse thread
Best way to choose an implementation of a lib ?
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2005-11-30 (16:25) |
From: | Stefano Zacchiroli <zack@b...> |
Subject: | how to detect .cmx incompatibility |
On Wed, Nov 30, 2005 at 09:19:30PM +0900, Jacques Garrigue wrote: > Directories seem a possible solution. > Note that with native code you must be careful to compile without any > .cmx around (only .cmi's), as this would induce dependencies on a > specific version. This also means that you lose inlining (one major > advantage of native code.) On this subject, is there a way to look at two .cmx and decide whether they link against a common module, but make different assumption about its implementation? With .cmos this is possible using the "objinfo" tool, but it does not work on .cmx .... TIA, Cheers. -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy zack@{cs.unibo.it,debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!-