Hello, > On Thu, 2005-06-02 at 10:42 +0900, Renaud BECHADE wrote: >> I guess this is a schema that happens very often� >> Lol > > It does happen quite a bit though. I'll admit that there are plenty of > parts in Classpath which are pretty poorly implemented. And there are > parts of Sun's implementation which seem very good.
How clean are the separations between packages/groups of packages in ClassPath? i.e. how possible would it be to use say java.sql.* with another implementation of java.lang? I ask this as I'm just wondering if having the ClassLoader select from multiple implementations based on user preference for that package would be a good idea or just an added complication. I see this as being of most use with the two cases you listed of specialist users and using native implementations. I suppose it possibly should be handled by the base ClassLib that contains the ClassLoader Class rather than at the primordial ClassLoader level. Thanks, Pete
