Fix incorrect macro in FT2Font setup.

[QuLogic]

This causes a warning about returning NULL as int.

However, I don't believe this call could even fail except in dire circumstances.

PR Checklist

• Has Pytest style unit tests
• Code is Flake 8 compliant
• [N/A] New features are documented, with examples if plot related
• [N/A] Documentation is sphinx and numpydoc compliant
• [N/A] Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
• [N/A] Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

[timhoffm]

I would like to approve so that this does not get lost, but I do not fully understand the issue. Can you plase give a little more context.

CALL_CPP_INIT returns an errorcode -1 instead of 0 in the case of CALL_CPP. What does this have to do with a warning about returning NULL as int?

[QuLogic]

Because NULL is not 0, it is (void *)0; using a pointer as an integer causes a warning.

[timhoffm]

But where is NULL coming into play here? The PR just changes the returned value from 0 to -1.

[QuLogic]

Ah, I see what you're asking; the NULL is there on the v3.2.x and older branches. But that aside, it's also more semantically correct since this is an _init function.