Some sort of scheme that checks which classes are package-private will help even more. We really should create a "compliance file" or set of files by running some variant of javap on Java's public and protected classes, and their public and protected members. Then we run that same program on our stuff and we discover any methods and fields we're missing, too. I'm curious: does everything that we have compile now (except security of course)? --John Keiser
- easily determining compliance Brian Jones
- Re: easily determining compliance John Keiser
- Re: easily determining compliance Brian Jones
- RE: easily determining compliance John Keiser
- RE: easily determining compliance Moses DeJong
- RE: easily determining compliance John Keiser
- RE: easily determining compliance Moses DeJong
- Re: easily determining compliance Aaron M. Renn

