Method Size Limit in Java
eblog.chrononsystems.com
eblog.chrononsystems.com
I had to literally abandon months of work on one project which was generating simulation code to Java. I was generating millions of lines of code, so splitting up the method would require a main method which would call all those split methods, and then that method would get too long, etc. It all just wasn't feasible, so now I just generate C.
Our database has garbage in it, but that limit's just insane.
2) Why bother? I mean generating C (in my case) was so much easier, a simpler solution (not using a tree) is bound to have less bugs, be easier to maintain etc.
I mean this is a fundamentally ridiculous limitation. One can work around it with a large amount of effort, but it shouldn't be necessary.
Often it is because of tag libraries that generate big try..catch..finally blocks.