Hi,
I'm trying to help others - not reporting a problem.
As an astronomer, I'm programming celestial mechanics routines - an implementation for the Android platform.
If you are aware, the size of data and routines are indeed very big in terms of size. The data, as an array, is not a problem - although it gives a lot of work to put it in that form. If you don't, you'll get modules with 40-500 Kb (depending of the theory you're using).
The size is not mesured with the bytes the b4a/java module has in Explorer. It can be much bigger. The INNER classes are the issue. Those do have a limit.
Solution: divide the best way the info and alghorithms in your inner Class Modules.
I was just trying to help others that might have this issue.
Apparently, my mistake.
Kind regards,
Kepler