PR 5803 - 0 vs nullptr

[Alan Carroll <so...@verizonmedia.com>]

Looking at this PR, it would be better if it could use "nullptr" instead of
"0", but that depends on the requirement that plugins be built with a C++
compiler. I know that's been discussed on and off and if I recall correctly
we did commit to that. Is my memory correct? Can we require a C++ compiler
for plugins?

Re: PR 5803 - 0 vs nullptr

[Walt Karas <wk...@verizonmedia.com>]

And thanks for outing Alan for talking behind my back (literally).

On Thu, Aug 8, 2019 at 4:34 PM Leif Hedstrom <zw...@apache.org> wrote:

>
>
> > On Aug 8, 2019, at 2:12 PM, Alan Carroll <
> solidwallofcode@verizonmedia.com> wrote:
> >
> > Looking at this PR, it would be better if it could use "nullptr" instead
> of
> > "0", but that depends on the requirement that plugins be built with a C++
> > compiler. I know that's been discussed on and off and if I recall
> correctly
> > we did commit to that. Is my memory correct? Can we require a C++
> compiler
> > for plugins?
>
>
> Well, I proposed that we’d do just that, but it was meant with resistance,
> so I dropped it. It’s no longer on the radar map for v9.0.0, but we can
> revisit for v10.0.0.
>
> So, no C++ in plugin APIs.
>
> Ciao,
>
> — leif

Re: PR 5803 - 0 vs nullptr

[Leif Hedstrom <zw...@apache.org>]

> On Aug 8, 2019, at 2:12 PM, Alan Carroll <so...@verizonmedia.com> wrote:
> 
> Looking at this PR, it would be better if it could use "nullptr" instead of
> "0", but that depends on the requirement that plugins be built with a C++
> compiler. I know that's been discussed on and off and if I recall correctly
> we did commit to that. Is my memory correct? Can we require a C++ compiler
> for plugins?


Well, I proposed that we’d do just that, but it was meant with resistance, so I dropped it. It’s no longer on the radar map for v9.0.0, but we can revisit for v10.0.0.

So, no C++ in plugin APIs.

Ciao,

— leif