From: Avery M. <av...@av...> - 2006-06-23 17:04:51
|
Hi, Status update: the initial package refactoring (including full preprocessor support), as outlined in my previous emails, is now complete. I am commencing ./build testing. One additional wrinkle, which I would like to elicit awareness and broader discussion (of which I expect many of you already anticipated): numerous package-protected classes and methods must have their modifiers changed to public, as RVM files are no longer in the same package. I am not aware of any (standards-compliant) technique to retain the existing protection modifiers, while also satisfying the package refactoring. I plan on generating a list of all resources which require such protection modification, for documentation and discourse purposes. Given many VM classes are already public, I do not believe this poses any incremental security risk over what already exists--but, this is a topic very worthy of list discussion and vetting. Are there compilation, build, linking, or execution implications of this protection modifier change that I should be aware? -a |