It would allow page designers to write non-spec compliant JSTL. Then if they switch JSTL implementations their non-spec compliant uses of the empty tag would break. However, I'm still for changing the implemenation to support empty on Collection. It doesn't break backward compatibility and it adds this new feature most users would assume was already there.
> -----Original Message----- > From: James Cook [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 14, 2003 9:17 AM > To: Tag Libraries Users List > Subject: Re: Problem with "empty" key word on a collection. > > > > On Thursday, February 13, 2003, at 05:04 PM, Pierre Delisle wrote: > > > The change that Jeff is proposing, although of interest, would > > unfortunately break compatibility with the spec. > > (sorry guys, but the Expert Group ain't perfect) > > > > Why would extending the empty keyword to support Collections break > compatibility with the spec? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
