On 2013-07-09, at 2:12 AM, Charles Oliver Nutter <head...@headius.com> wrote:
> We advise our users to pass in a classloader. Class.forName's > stack-based discovery of classloaders is too magic anyway. It has long seemed like a bit of a crock that classloaders were not part of the class name. Some of the squirreliest bugs we had in the Fortress implementation occurred when "the" classloader somehow got itself duplicated, and the "Foo is not a Foo" errors were the worst. David _______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
