On Wed, 12 Jun 2002, Ian Darwin wrote: > For one thing I don't think a LOT of people actually specify the buffer size > (of course those who DO will jump in to prove me wrong, and those who > don't will remain silent :-)). > > For another, memory is getting bigger quickly, and having sizes of things > specified unambiguously - in such a way that it can be understood by > someone who can't quote the spec from memory - is a Good Thing.
Well, having the 'kb' suffix will certainly avoid confusion for the metric-system people ( who may believe that's in kilograms or kilometers ). It is certainly confusing for programmers ( were most of the time the 'k' suffix is used, and the default suffix is optional ). I'm very sensitive to backward compatibility, and it drives me crazy when I see this kind of changes - I understand deprecating Thread.stop(), or things where any decent argument exists, but changing a syntax in an incompatible way for estetic reasons is unacceptable. As for the pages that'll brake - well, tomcat4.0 examples ( part of the JSP1.2 RI ! ) are one case ( see include.jsp ). Note that the size was already ( in jsp1.1 ) in kilobytes, the only change is in 1.2 is to make it mandatory to use a 'kb' suffix ( and thus ilegal to use the previously legal values, without kb ). I know strict compliance is important ( almost as important as backward compatibility on my scale ), and the bug is not in jasper but in the spec. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
