Re: get/setDocumentURI in org.w3c.dom.Document

/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say:
| * Norman Walsh wrote:
|>As far as I can tell, something about the process that generated those
|>API files caused the documentation for each get* method to be
|>textually identical to each set* method. Is that not a bug?
|
| No, the Java bindings are automatically generated from the specification
| source code, which only documents attributes as attributes, not as indi-
| vidual methods. For attributes that are read/write you inevitably get in
| some cases odd documentation. I don't think it is feasible to write two
| versions of the text for all such attributes, and I don't see an easy
| way to automatically generate more suitable text.

That's unfortunate. I wonder if it would be possible to add an
explanation of the problem to the description of the class at the top
of the file? At least that way readers would know it was intentional
and not a documentation bug.

| There are indeed two mails from you in the archive, expect them to be
| addressed as the specification is being revised.

Right. Good. I sent one more simple typo in this morning, in a
separate message so that it would be easier to track. If others come
up, I'll make sure they get reported.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | If you run after wit you will succeed
http://nwalsh.com/            | in catching folly.-- Montesquieu