one?
You shouldn't expect System.identityHashCode() to be usable as
a UID. Assuming otherwise is non-portable ... as you've just
discovered.
Cheers,
Miles
--
Miles Sabin Cromwell Media
Internet Systems Architect5/6 Glenthorne Mews
+44 (0)20 8817
wers.
> You also might want to read a paper we wrote recently about
> engineering systems for high throughput.
Looks very interesting from a quick scan. It looks like we're
going in pretty much the same direction.
Cheers,
Miles
Ps. Looking forward to working with you
Godmar Back wrote,
> Miles Sabin wrote,
> > [snip: className.class vs Class.forName("className")]
>
> In other words, you're saving a try/catch clause at the
> expense of one hidden static variable.
Hmm ... well, a litte more than that. The lookup is done
on
> If you know the class' name, and I suspect that you do
> since you are in a static method of the class, you can
> do a Class.forName(className).
Better still, className.class, and have it resolved at
compile time rather than by a runtime lookup.
Cheers,
Miles
-
to substitute anything comparable.
Within the terms in which you phrased the question I
guess the answer has to be "because it's convenient",
but I think it goes a bit deeper than that.
Cheers,
Miles
--
Miles Sabin Cromwell Media
Internet
