God, I wish I could type. "I *don't* think forcing HasValue to take a stand on that issue is helpful." Basically, in some spots "empty" is meaningful and in other it isn't. In some of those spots null will make sense, and in others it won't. I don't think there is a general problem to be solved there, and if there is I don't think HasValue is the place to solve it.
rjrjr On Mon, Dec 1, 2008 at 3:37 PM, Ray Ryan <[EMAIL PROTECTED]> wrote: > I don't buy the argument that the current interface can't be used or > implemented reasonably. > The only real issue here, I think, is about the use of null. Trying to > broaden that discussion to take on filtering legal non-null values is an > artificial expansion of the problem. > > Not all widgets can be cleared meaningfully. Consider a select > element--it's always showing something. I think forcing HasValue to take a > stand on that issue is helpful. > > rjrjr > > On Mon, Dec 1, 2008 at 3:28 PM, John Tamplin <[EMAIL PROTECTED]> wrote: > >> On Mon, Dec 1, 2008 at 6:26 PM, Ray Ryan <[EMAIL PROTECTED]> wrote: >> >>> That way lies data validation, something GWT needs, but something I think >>> we're not ready to cram into 1.6. >> >> >> If the alternative is to come up with either something that can't be >> implemented reasonably or something else that can't be used reasonably, I >> don't see the point in including it at all. >> >> >> -- >> John A. Tamplin >> Software Engineer (GWT), Google >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
