Re: [WEBIDL] [Undefined] sample
Anne van Kesteren: The example for [Undefined] should probably say [Null=Null, Undefined=Null] because just saying [Undefined=Null] doesn't make much sense. Because why would you want undefined to map to null, but null to map to null? Or because undefined would map to null, which then would in turn map to null? (The latter isn’t my intention.) -- Cameron McCormack ≝ http://mcc.id.au/
Re: [WEBIDL] [Undefined] sample
On Thu, 22 May 2008 13:22:50 +0200, Cameron McCormack [EMAIL PROTECTED] wrote: Anne van Kesteren: The example for [Undefined] should probably say [Null=Null, Undefined=Null] because just saying [Undefined=Null] doesn't make much sense. Because why would you want undefined to map to null, but null to map to null? Yeah, that's seems odd. Or because undefined would map to null, which then would in turn map to null? (The latter isn’t my intention.) I didn't think of this one, that seems even weirder :-) As a data point, for XMLHttpRequest a shorthand for [Null=Null, Undefined=Null] would be nice. That's the only one of this [Null]/[Undefined] madness I need and I have to write it out four times. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/
Re: [WEBIDL] [Undefined] sample
Anne van Kesteren: The example for [Undefined] should probably say [Null=Null, Undefined=Null] because just saying [Undefined=Null] doesn't make much sense. Cameron McCormack: Because why would you want undefined to map to null, but null to map to null? Anne van Kesteren: Yeah, that's seems odd. OK, changed it. Or because undefined would map to null, which then would in turn map to null? (The latter isn’t my intention.) I didn't think of this one, that seems even weirder :-) As a data point, for XMLHttpRequest a shorthand for [Null=Null, Undefined=Null] would be nice. That's the only one of this [Null]/[Undefined] madness I need and I have to write it out four times. Suggestions welcome. :-) -- Cameron McCormack ≝ http://mcc.id.au/
