Hi Raffaello,
Sharing one class as a holder for many methods would be worth looking at
if
the class overhead became significant. Concerns would be in making sure
replaced methods are collected and in housekeeping.
If John moves to providing a 'method loader' then this would be something
to look into though I would probably just keep an array of method handles.
Hopefully there would be no links from the class to the method which would
prevent GC.
For now it does not seem to be an issue. The next time I find myself
doing
profiling I may take a look at the memory usage
regards
mark
_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
