On May 5, 2004, at 12:06 PM, Dan Sugalski wrote:
At 7:57 PM +0100 5/5/04, Nicholas Clark wrote:On Wed, May 05, 2004 at 08:59:03AM -0400, Dan Sugalski wrote:
Yeah, that's what I'm figuring. The symbols themselves should be cross-platform, modulo the odd prefix character, or so I hope. The linker magic is definitely going to be platform and linker specific--we may have to throw in a config/auto/linker.pl file to identify the linker, along with linker-specific config modules.
Which implies that platforms may exist where it's not possible to do this.
(surely?)
Possibly. I'm tempted to burn that bridge when we actually get to it, if we ever do, at which point we have to do all sorts of nasty stuff with preprocesor macros.
Yeah, the approach which ICU uses for symbol renaming (see the most recent messages on the "Outstanding parrot issues?" thread) should work for all platforms. Linker tricks will only work for the dynamic library version anyway (but are probably worth doing where we can), so to support a ".a" version of libparrot we'd need something such as that anyway. (That is, with archive libraries I don't think there's any linker magic we can do while building the library, though there may be magic which could be done when subsequently using it.)
JEff
