> I was wondering if there is an argument against using initialize ==
> true in all cases?
Here are a couple of examples, in the strictly java world (java
programming language and vm) when you want initialize to be false.
The idiomatic use case being byte code analysis
* FindBugs
* Code obfuscat
On Oct 26, 11:18 am, "Stephen C. Gilardi" <[EMAIL PROTECTED]> wrote:
> RT/classForName currently hardwires the "initialize" option of
> Class.forName to false. In working with jdbc drivers, the need to
> initialize classes in some circumstances came up--in some JRE
> configurations, the driver c
