Re: [cp-patches] Stupid spec constant values

[Tom Tromey]

>>>>> "Stuart" == Stuart Ballard <address@hidden> writes:

Stuart> Putting the values in, stupid and ridiculous as they are, costs us
Stuart> nothing, but it eliminates a false positive in the errors so that the
Stuart> *real* errors stand out more.

Yeah.

Stuart> Exactly - in other words, code working as you (Mark) described would
Stuart> fail anyway, unless we actually moved our implementations into a
Stuart> sun.rmi.server package. Since this is purely hypothetical code we're
Stuart> talking about, I'd not bother, but if any actual such code showed up,
Stuart> that's what we'd have to do.

Yeah, or do bytecode rewriting in the class loader :-)

Stuart> Sun has a whole "constant field values" page in their documentation
Stuart> and all these values are listed there - even the RCSIDs.

I've always assumed that this page is auto-generated by javadoc,
which unfortunately doesn't know how to distinguish the dumb
constants ;-)

I think this patch should go in.  Perhaps the javadoc comments could
use an '@specnote' before the text explaining the lameness of these
fields?

Tom