0029006: Coding Rules - define Standard_NULL to replace NULL

Issue History
Date Modified	Username	Field	Change
2017-08-16 17:44	Vico Liang	New Issue
2017-08-16 17:44	Vico Liang	Assigned To	=> kgv
2017-08-17 13:38	kgv	Priority	normal => low
2017-08-17 13:38	kgv	Severity	minor => feature
2017-08-17 13:39	kgv	Summary	Define Standard_NULL to replace NULL => Coding Rules - define Standard_NULL to replace NULL
2018-10-01 08:30	kgv	Assigned To	kgv => abv
2018-10-01 08:30	kgv	Status	new => feedback
2018-10-01 12:51	kgv	Note Added: 0079557
2018-10-02 09:52	msv	Note Added: 0079571
2018-10-02 15:16	abv	Note Added: 0079600
2018-10-02 15:16	abv	Assigned To	abv => Vico Liang
2018-10-02 15:16	abv	Note Edited: 0079600	View Revisions
2018-10-03 17:21	Vico Liang	Note Added: 0079649
2018-10-03 17:23	Vico Liang	Assigned To	Vico Liang => kgv
2018-10-03 17:23	Vico Liang	Status	feedback => acknowledged
2018-10-03 18:25	abv	Note Added: 0079653
2018-10-03 18:25	abv	Status	acknowledged => closed
2018-10-03 18:25	abv	Resolution	open => no change required

Notes
(0079557) kgv (developer) 2018-10-01 12:51	Dear colleagues, please share your opinion about this feature.

(0079571) msv (developer) 2018-10-02 09:52	What benefits will it bring?

(0079600) abv (manager) 2018-10-02 15:16 edited on: 2018-10-02 15:16	I deem 0 can represent NULL pointer pretty well. I understand that there is some rationale behind nullptr, but prefer not to define our own alternative. Let's wait until we abandon support of VS 2010 and then we can use standard nullptr.

(0079649) Vico Liang (developer) 2018-10-03 17:21	nullptr is supported in most modern C++ compiler. No objection to use standard nullptr.

(0079653) abv (manager) 2018-10-03 18:25	Yep, nullptr is supported by VS 2010, sorry for mistake. Thus there is no issue - we can use nullptr. I am closing the issue.

Relationships