The RC2 has far fewer dependencies (about 6 in non-util classes). The code switcher method is the only way we can use the same source that is JAVA2 / JDBC2 by default but can switch to JAVA 1.1 or JAVA 1.4 with JDBC3. Providing duplicate sources introduces its own problem of synchronisation when the code is patched and can result in errors going undetected.
Fred Toussi ----- Original Message ----- From: "Ulrich Vollert" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 23, 2002 3:20 PM Subject: [Hsqldb-developers] Future of CodeSwitcher > Hi, > > the CodeSwitcher.class for hsqldb is a bit tricky (or nasty, as you > like ;-)). It doesnt fit into the Java Philosophy. But I would like to > preserve the sources for JDK 1.1. > > (BTW: Have you seen the brand new PDA Zaurus by Sharp? It runs with > Linux (!), but the JDK is 1.1.) > > What plans do you have concerning the CodeSwitcher? > > I am not sure: would it be a better solution to define different > subclasses which contains different sources as in the following > classes: > > jdbcConnection.java:5 > jdbcDatabaseMetaData.java:14 > jdbcPreparedStatement.java:21 > jdbcResultSet.java:88 > jdbcStatement.java:10 > > (the number is the number of occurences of 'ifdef JAVA2') > > to differentiate JDK 11 and 12 and have different classes to compile? > > This would be easier to integrate into Ant, too. But I havent spent > enough time with the sources to judge this problem right. > > What do you think? > > Regards, > Ulrich > > _______________________________________________ > hsqldb-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hsqldb-developers _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
