Fix build warnings in NEPs

[rgommers]

No description provided.

[rgommers]

I'm not sure what the intent here was, I assume what I replaced it with but this looked pretty weird.

[charris]

I think you got it right, but it is a bit odd to use the same name for two different structures.

[eric-wieser]

I can't work out what your comment is referring to @charris. What name and which structures?

[charris]

Looking in the code, there doesn't seem to be anything like this, so I expect it has marginal relevance to how the implementation ended up. The closest thing I could find is

/* Internal-only AXISDATA MEMBER ACCESS. */
struct NpyIter_AD {
    npy_intp shape, index;
    npy_intp ad_flexdata;
};

Where ad_flexdata seems to be either a stride, or a pointer stored as an integer. It's probably going to cause trouble eventually.

[charris]

@eric-wieser It looked like struct axis_data could contain different entries depending on a flag, I think NpyIter_AD has the same dual use of ad_flexdata.

[rgommers]

Thanks for checking. I think no need to look into it more. Just to document why I changed it:

• it caused a Sphinx warning
• it caused code highlighting for the whole code block to go missing

[charris]

Thanks Ralf.