[quote]How about a class that stores its bytecode in a byte[] array, and creates its own classloader to load & resolve the embedded class, and then delegates all its private internal workings to the embedded class by using reflection?
Cas 
[/quote]
I think using reflection probably has to be outlawed in the Java Obfuscation Competition for the same reasons the pre-processor is outlawed in the C contest.
It just makes it too easy
[quote]well it could do a call to:
private native Object randomUnmaintainableCodeAcceptingAllArguments(Object data);
which was implemented in pure asm ;D
[/quote]
You have that code wrong.
It’s
private native int calllllllAndBlastOutWindoze(ByteBuffer b);
private native windowsPerformedAnillegalOperationAndMustBeShutDown(ByteBuffer _buffer)
{
int nonsense = 0xFF11AE;
System.out.println(“BUFFER OVERFLOW EXCEPTION IN ADDRESS NONSENSE” + nonsense);
System.exit(1);
}
You can’t implement native methods.
Now you can. ;D
[quote]Yeah… this nonsense is filed under Off Topic for a reason :).
Besides, only My opinion matters ;D
[/quote]
Seconded.
Java 1.5 beta enters the mix…
Someone at Sun apparently doesn’t like the
if( something
|| something
&& something )
{
...
}
…because the stack traces for runtime errors collapse that multi-line if check into a single line before reporting the number. With a code numbering editor, you will be told that the runtime error is in the “if( something” line, even if it isn’t.
I only noticed because I was getting:
in the line
if( myVariable != null
LOL!
[although, obviously, this is a bug with the 1.5 beta (line numbering for stack traces has to take into account EXACT source layout - including all blank lines as significant etc).]