I have some ltdl patches to current Japhar. I implemented it as yet another DLL API, enabled with --with-ltdl. I also added a monitor to make DLL handling thread save. It seems to work fine, and I beleave using it will make part of our DLL api obsolete. I suggest moving to the new dll handling in this order: - I commit the current patch implementing yet another DLL API - We test this with Classpath and on all supported platforms. - If it is working, we throw away the other DLL APIs and use only ltdl. - Last we may remove the dynamic loading from libarch, using ltdl directly. Any comments? As far as I know, Japhar is only tested to work on Linux, FreeBSD, Solaris using our DLL handling. It works on BeOS using NSPR, and not yet on Win32 (incomplete port) and HP/UX (missing threads). Is it working on Irix? I beleave ltdl is tested to work on Linux, FreeBSD, Solaris, Irix, BeOS, Win32 and HP/UX, so using it does not shorten our ports list. -- ##> Petter Reinholdtsen <## | [EMAIL PROTECTED]
