El lun, 06-01-2014 a las 14:19 -0800, Martin Robinson escribió:
> On Mon, Jan 6, 2014 at 1:16 PM, Ryosuke Niwa wrote:
> > Sounds like a great idea to me.
>
> Seconding this. nullptr also has much better compatibility with varargs than
> 0.
Yeah, with nullptr we don't need the coding style excep
On Mon, Jan 6, 2014 at 1:16 PM, Ryosuke Niwa wrote:
> Sounds like a great idea to me.
Seconding this. nullptr also has much better compatibility with varargs than 0.
--Martin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.
Sounds like a great idea to me.
- R. Niwa
On Mon, Jan 6, 2014 at 12:04 PM, Anders Carlsson wrote:
>
> On Jan 6, 2014, at 12:01 PM, Dan Bernstein wrote:
>
> >
> >
> > Sent from my iPad
> >
> >> On Jan 6, 2014, at 11:55 AM, Darin Adler wrote:
> >>
> >> I suggest we use nullptr, rather than of
On Jan 6, 2014, at 12:01 PM, Dan Bernstein wrote:
>
>
> Sent from my iPad
>
>> On Jan 6, 2014, at 11:55 AM, Darin Adler wrote:
>>
>> I suggest we use nullptr, rather than of 0 or NULL, for all pointer nulls in
>> WebKit C++ sources. I don’t see any advantage to using 0 or NULL over
>> nul
Sent from my iPad
> On Jan 6, 2014, at 11:55 AM, Darin Adler wrote:
>
> I suggest we use nullptr, rather than of 0 or NULL, for all pointer nulls in
> WebKit C++ sources. I don’t see any advantage to using 0 or NULL over
> nullptr, and nullptr has multiple advantages. Three obvious ones: Com
I suggest we use nullptr, rather than of 0 or NULL, for all pointer nulls in
WebKit C++ sources. I don’t see any advantage to using 0 or NULL over nullptr,
and nullptr has multiple advantages. Three obvious ones: Compile time error if
accidentally passed to something expecting an integer, can be
6 matches
Mail list logo