On Jul 11, 2012, at 10:02 PM, Glenn Maynard wrote: >> > What's the main problem with it being nullable? A fabricated date seems > strange, but instead of being nullable we could spec what the fabricated date > is. I'm just not totally sure what the pros and cons are here. > > If you call "d.getYear()" and d is null, you get an exception, which has a > very high chance of breaking the app if it's not checked for. Giving an > arbitrary (but well-defined) default is much less likely to break things that > badly. This is much more important when the null case is rare, because > nobody is going to remember to test for it. > > Can you log a bug so that I can provide guidance for this in spec? > > Sorry, but to avoid rereading the thread, a bug for what exactly? Do you > need anything beyond https://www.w3.org/Bugs/Public/show_bug.cgi?id=17746?
Bug 17746 is for better definitions of snapshots. I minted Bug 17762 (https://www.w3.org/Bugs/Public/show_bug.cgi?id=17762) to replace a nullable Date with something better. Strawperson suggestions welcome for what this arbitrary date should be, or else I may arbitrarily choose an unlikely Towel Day in the past (http://towelday.org/ -- don't panic). > -- A*
