>The code runs fine under jdk 1.1, but requires java 2 to compile. It was decided that >this was OK.
If this is really the community consensus, I can live with it, but I don't remember seeing warning/discussion of that decision in the xerces-j-dev or xalan-j-dev groups. If it did appear, please feel free to point me to archives; if it didn't we should probably pause to check with the users before adopting it. >How important is being able to compile on JDK 1.1.x to you? There are still folks developing/debugging under tools which are locked into 1.1. Not being able to compile under 1.1 would also be a nuisance when attempting to diagnose and fix problems related to running under 1.1, such as the collections-classes calls. Both can probably be overcome with sufficent context-switching, but I'm somewhat reluctant to go that route unless there's a strong reason to do so -- a major performance gain or some such clear benefit. Since the bootstrapping process is (obviously) not inner-loop code, I don't see this specific change as offering enough benefit to justify the cost. One man's opinion. Your milage may vary. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
