Jump to content
  • Advertisement
Sign in to follow this  
Thygrrr

J2ME Preverification before Obfuscation

This topic is 4952 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Preverifying my .jars and then feeding them to ProGuard will result in roughly 1k saved space compared to when doing it the other way around. However, after a file has been obfuscated, changes have been made to it, so technically, it's not really preverified anymore, is it? In which order should the Obfuscator and Preverifyer be invoked? [Edited by - Thygrrr on November 27, 2004 9:49:38 AM]

Share this post


Link to post
Share on other sites
Advertisement
If you preverify then obfuscate, it will save space.

Unfortunately it won't actually then work.

I'm not sure exactly what preverifying does, but I think it adds a little extra info to the class files to make them work on J2ME.

Obfuscation throws that away and thus breaks it completely.

So always preverify last.

Mark

Share this post


Link to post
Share on other sites
Yes, I was encountering problems on some handsets with "obfuscated last" code, IIRC.

I currently make do with data driven design, so I rarely have to squeeze out single kbytes from my jars, anyway. It was an academic question, so to speak :)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!