Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix type warnings with strict gcc #394

Merged
merged 2 commits into from
Jun 10, 2024
Merged

fix type warnings with strict gcc #394

merged 2 commits into from
Jun 10, 2024

Conversation

esheldon
Copy link
Owner

No description provided.

Comment on lines 3606 to 3629
PyObject* columnsobj=NULL;
PyObject* array=NULL;

PyObject* rowsObj=NULL;
PyObject* sortindObj=NULL;
PyObject *columns_obj, *array_obj, *rows_obj, *sortind_obj;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we want to get rid of the NULL initialization here?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are immediately read into by the module initialization, so its OK in this case. I did it for readability. But if you don't like I'm happy to set NULL

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

by module init I meant things like PyArg_ParseTuple

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Never mind, I'll just set NULL

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right I don't care, I just wanted to flag it.

Copy link
Collaborator

@beckermr beckermr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some of the null inits have been removed. IDK if we want to do this or not?

@esheldon esheldon merged commit 7ecda4b into master Jun 10, 2024
34 checks passed
@esheldon esheldon deleted the type-warnings branch June 10, 2024 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants