- From: Joseph Kesselman <keshlam@us.ibm.com>
- Date: Tue, 21 Aug 2001 13:03:43 -0400
- To: "Curt Arnold" <carnold@houston.rr.com>
- Cc: <www-dom-ts@w3.org>
>The one test == one Java file/class flows out of that since it is most >natural to do a case by case conversion using XSLT. I Many-to-one isn't all that much harder, using XSLT's document() function. You'd want a top-level document which said which tests were to be built into each class, but that's easy enough. I have no opinion right now re which approach is better. This may depend on what the surrounding test framework looks like, and what your plans are for releasing deltas as the tests improve. >characterdataappenddatanomodificationallowederr Some compilers, in some languages, have trouble with long symbol names, even when the language permits them. I've seen some which simply ignore any characters beyond the first (or last) 32. We may want to consider adopting a set of standard abbreviations to avoid that risk. " chardataappendnomoderr" would cut the length by about 50%, though I grant that it's less readable for a novice. (Of course, readability of those names is rather marginal anyway. I presume people have already considered camelCasedNames...?) ______________________________________ Joe Kesselman / IBM Research
Received on Tuesday, 21 August 2001 13:04:22 UTC