Fix c curl generator

[amoweb]

Fix for issue #21092

PR checklist

• Read the contribution guidelines.
• [ x Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in Git BASH)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@eafer

[eafer]

Hi! I just took a quick look at the new generated samples, and I see that petId for deletePet becomes a pointer. What's the point of that? The petId is not nullable, right?

[eafer]

Also, would you mind adding some tests for these issues to the petstore.yaml for C? That would make it much easier to understand what you are doing, and it would prevent other people from breaking this again in the future.

[amoweb]

Hi! Thanks for your answer @eafer ! Considering your comments, I changed the strategy. I added an example in petstore.yaml and I no longer change the function signature.

[eafer]

Thanks. I can see a new UserAPI_testInt32Int64FloatDouble() function in the generated samples, but I'm not seeing the changes to the yaml file that made that happen. Am I missing something, or maybe you forgot to commit that?

[amoweb]

Sorry. I commited the missing yaml file.

[eafer]

Thanks. Why did you set MAX_NUMBER_LENGTH_FLOAT to 32, is this an arbitrary limit? For big float numbers the output of snprintf() will be off. I think in this case it would be better to call snprintf twice, the first time to get the size of the buffer needed.