[vtk-developers] Use of nullptr

Bill Lorensen bill.lorensen at gmail.com
Wed Feb 1 11:40:44 EST 2017


There is. backdoor to disable c++11 on the current VTK build.


On Wed, Feb 1, 2017 at 11:19 AM, Marcus D. Hanwell
<marcus.hanwell at kitware.com> wrote:
> To the best of my understanding this is the one feature we actually
> test for and require of C++11 at this stage. I have a 2010 Macbook Pro
> that I am able to compile this on, but it is on Sierra mist...
>
> On Wed, Feb 1, 2017 at 11:00 AM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> I run an old Mac release. I guess it's time to upgrade... Something to do
>> while my new hip heals.
>>
>> On Feb 1, 2017 10:53 AM, "Marcus D. Hanwell" <marcus.hanwell at kitware.com>
>> wrote:
>>>
>>> On Wed, Feb 1, 2017 at 8:59 AM, Bill Lorensen <bill.lorensen at gmail.com>
>>> wrote:
>>> > Recent changes to files in GUISupprt/Qt use nullptr, which is a c++11
>>> > construct. I know we are moving to c++11, but for the time being it
>>> > seems that nullptr could be replaced will NULL in these two files
>>> > without any impact.
>>> >
>>> I was under the impression we had already moved to C++11, and it
>>> seemed like a reasonable thing to use. I can replace it with NULL if
>>> that is preferred, sorry if I jumped the gun on moving forward with
>>> this.
>>>
>>> What is the reasoning not to use it though, our CMake files require
>>> C++11 and this was one of the first things added to compilers from
>>> C++11 when it was 0x.
>>>
>>> Thanks,
>>>
>>> Marcus



-- 
Unpaid intern in BillsBasement at noware dot com


More information about the vtk-developers mailing list