On Tue, Jan 23, 2007 at 12:16:06PM +0100, Mark Brouwer wrote: > Peter Jones wrote: > >> The biggest concern that I can think of right now, which would argue >> for this approach being only optionally enabled, is that it would >> deoptimize (with respect to the current implementation) the case of >> the first URL in the codebase pointing to a JAR file that definitely >> does not exist, which (as previously described) is not intended to >> necessarily result in an overall class/resource loading failure. Not >> that the importance of that case is obvious... > > I think you shouldn't have made that last remark ... It will be hard to > tell the overall effect but for now I make it optionally. If somebody > else has a take on this please mention it.
My wording and ellipsis were admittedly vague-- I was actually about to write that it didn't seem worthwhile to me to bother making the proposed behavior conditional on a system property, and then I thought of the above case and decided to mention it for the record. But even though it is "the biggest concern that I can think of right now", I'm not currently seeing it as big enough to worry about. -- Peter
