[vtk-developers] Use of nullptr

[Bill Lorensen]

I understand. I have upgraded my Mac OS to Sierra which is c++11 compatible.

Sorry for the noise.


On Mon, Feb 6, 2017 at 2:43 PM, Robert Maynard
<robert.maynard at kitware.com> wrote:
> I should clarify the intent of this backdoor.
>
> The backdoor is meant to allow people to compile VTK with C++11
> enabled when using a compilers that CMake has no knowledge of. For
> example CMake doesn't know how to enable C++11 on the PGI compiler
> currently so you can use this backdoor/workaround to get VTK + PGI +
> C++11 building. Using this workaround to disable C++11 support will
> not be a valid use case going forward.
>
> On Wed, Feb 1, 2017 at 11:40 AM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> 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
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at: http://markmail.org/search/?q=vtk-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/vtk-developers
>>



-- 
Unpaid intern in BillsBasement at noware dot com