This statement is dead on obvious but my problem is: I need to call this method: someMethod (java.lang.Class type, java.lang.Object value)
Scenario 1: (Works) boolean bP = true Boolean bW = new Boolean(bP); someMethod( Boolean.class, bW ); //ok Scenario 2: (Compile error) someMethod( boolean.class, bP ); //error Is there any way to coerce scenario #2 to work? Pho
I know this is of no importance here but... In C#, primitives can be treated as objects transparently.
Tony Alicea Senior Java Web Application Developer, SCPJ2, SCWCD
posted 17 years ago
Tony. . . naughty, naughty - reading up on microsoft stuff when no one is looking . So are they really primitives and the language disguises that (I think not) or did they make everything a true object??? It is really just the primitives, the special handling of strings, and arrays that prevent java from being a pure object oriented language. How many concessions did C# make???
"JavaRanch, where the deer and the Certified play" - David O'Meara
Amateurs built google. Professionals built the titanic. We can't find the guy that built this tiny ad:
Programmatically Create PDF Using Free Spire.PDF with Java