[Nfd-dev] code style rule 3.20

Junxiao Shi shijunxiao at email.arizona.edu
Thu Oct 30 15:00:31 PDT 2014


Hi Alex

I'm not saying 0 is forbidden.

My suggestion is: any new code should use nullptr to represent null
pointer, instead of 0 or NULL.

Yours, Junxiao
On Oct 30, 2014 2:57 PM, "Alex Afanasyev" <alexander.afanasyev at ucla.edu>
wrote:

> Given the amount of code we have, I would suggest we keep both notations
> as allowed.
>
> On Oct 30, 2014, at 2:49 PM, Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
>
> Dear folks
>
> rule 3.20 states: 0 should be used instead of NULL.
>
> In C++ 11, a null pointer is typically written as std::nullptr.
> Usage of std::nullptr is already permitted, because it doesn't violate
> this rule.
>
> Should we amend this rule as follows?
> "std::nullptr" should be used to represent null pointer.
>
> Yours, Junxiao
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141030/fe054e0e/attachment.html>


More information about the Nfd-dev mailing list