On Wednesday 07 January 2004 00:05, Berin Loritsch wrote: > Niclas Hedhman wrote: > > Open for arguments...
I see a list of "why not, not do it" (I just love double negation), which doesn't imply "why to do it". Let's see in detail what we can dig out of these arguments; > I understand the concerns, but currently the model we have has to be > altered, which also may require alterations to the composition package > (speculation here). "Has to be altered"? Please provide some info about this requirement. > Not to mention that the Merlin is not currently geared > for the JDK 1.5 approach. This is against an alternative approach. > Our utility would be able to function--even in a > 1.5 environment. This is a "feature" that is only relevant after the decision to 'roll our own'. > Not to mention, if there are changes that need to be done > to the Attribute classes, that refactoring would be easy to accomplish. Not sure what you are referring to here. The Attribute classes, are the ones that would exist after the fact. Still no news on why to do it in the first place. > Not to mention JDK 1.5 availability rolls out in stages, usually on > WIndows/Sun platforms first, followed by a few months later with Linux, and > even later OpenBSD and Mac. We would be able to maintain users forced to > remain on 1.4 for the forseeable future. Again, an argument between two alternate solutions, of I see no remarkable evidence I need in the first place. Sorry Berin, I think you missed the target - Why do it in the first place? Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
