On 9/12/05, David Holmes <[EMAIL PROTECTED]> wrote: > Raw types make things very messy. I think your are confusing the nesting > aspects and the inheriting aspects of types.
You're not kidding that they're messy ;) I don't think I was exactly confusing the nesting and inheriting aspects, just misunderstanding the "all or nothing" requirement. I thought it applied "globally" so you couldn't use a raw type inside a generic containing class because that would be partially qualified from a global point of view. >From japitools point of view it does make things a little complex to deal with because of the way japi files represent these things - it does lead to situations where japitools' representation will have to act as if some types are bound and some unbound. But I can see how from the Java language perspective this doesn't apply. > Hope this helps. It certainly does. Thanks! Stuart. -- http://sab39.dev.netreach.com/ _______________________________________________ Classpath mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath
