(hope you don't mind me ccing the list) On 10/4/05, David Holmes <[EMAIL PROTECTED]> wrote: > If a public or protected member utilises a type that it not public or > protected then that is a bug in the API. Unfortunately Sun has not responded > to these bugs - eg GridBagLayoutInfo - in the past six years.
Sun unresponsive? Never! Say it ain't so! > Other than treat these inaccessible types as objects, no program could > effectively make any use of them. > > That doesn't really help with your predicament however. I think it does... it's a datapoint in favor of excluding them from the japi file which is the way I was leaning already. The one I'm most nervous about excluding (although I don't know if it ever actually comes up) is inaccessible thrown exceptions. You can always catch those by just catching them as Exception, so the method is usable. On the other hand it would guarantee an API error because the Free implementation would be completely unable to provide the same throws clause. Perhaps Japize should go and find the nearest public superclass of the inaccessible exception type and pretend that that was what appeared in the throws clause... Stuart. -- http://sab39.dev.netreach.com/ _______________________________________________ Classpath mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath
