Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
От
Lew
Тема
Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet
Дата
Msg-id
ip48de$abj$1@news.albasani.net
Ответ на
Re: Unnessecary use of new Integer(n) in
AbstractJdbc2ResultSet (Kevin Grittner)
Список
Дерево обсуждения
Re: Unnessecary use of new Integer(n) in
AbstractJdbc2ResultSet "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet Kris Jurka <books@ejurka.com>
Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet Lew <noone@lewscanon.com>
Re: Unnessecary use of new Integer(n) in
AbstractJdbc2ResultSet "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Unnessecary use of new Integer(n) in
AbstractJdbc2ResultSet "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet Lew <noone@lewscanon.com>
Kevin Grittner wrote: > Lew wrote: >> Yeah, you have to use -bootclasspath to get the right rt.jar if >> you use -target. > > I guess I didn't make my point very clearly. I don't want to > compile with an *earlier* target. The *default* is to compile with > the earlier bytecode target. It won't actually *run* on the earlier > JVMs because we're using the later API, so we're just hurting > performance by *not* forcing the '-target 1.4' for -jdbc3 and > '-target 1.6' for -jdbc4. > > If you don't believe me, look at this page for the bytecode level Oh, I believe you! -- Lew Honi soit qui mal y pense. http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg
В списке pgsql-jdbc по дате отправления
От: Kevin Grittner
Дата:
От: Kevin Grittner
Дата: