Re: i18n API - Invalid option values should not throw

2012-09-05 Thread Norbert Lindenberg
Hi Marcos, I have a few more comments on your comments below, but here's the main important reason for exceptions: They are the prerequisite for compatibly introducing new values over time. The issue is: If we assign a default behavior to values that aren't explicitly described in the spec,

Re: i18n API - Invalid option values should not throw

2012-09-05 Thread Marcos Caceres
Hi Norbert, On Thursday, 6 September 2012 at 00:04, Norbert Lindenberg wrote: Hi Marcos, I have a few more comments on your comments below, but here's the main important reason for exceptions: They are the prerequisite for compatibly introducing new values over time. The issue is:

Re: i18n API - Invalid option values should not throw

2012-09-03 Thread Marcos Caceres
(accidentally left out es-discuss when I responded to Norbert… response if below) On Monday, 3 September 2012 at 13:20, Marcos Caceres wrote: Hi Norbert, On Saturday, 1 September 2012 at 00:31, Norbert Lindenberg wrote: On Aug 31, 2012, at 7:17 , Marcos Caceres wrote: The way

i18n API - Invalid option values should not throw

2012-08-31 Thread Marcos Caceres
Hi, I have a strong concern about the i18n API throwing an exception when an unknown value is given as part of the option parameter for a constructor or function. For example, if I do: new v8Intl.DateTimeFormat(x, {year: long}); or: x.toLocaleTimeString(en, {year: long}); I get in Chrome:

Re: i18n API - Invalid option values should not throw

2012-08-31 Thread Norbert Lindenberg
Hi Marcos, Thanks for the comments. Replies below. Norbert On Aug 31, 2012, at 7:17 , Marcos Caceres wrote: Hi, I have a strong concern about the i18n API throwing an exception when an unknown value is given as part of the option parameter for a constructor or function. For example,