Does this patch look okay for me to go ahead and commit?
Thanks, Seth
That did initially occur to me but I saw the matchesType usages in a few other locations and wanted to keep a compatible API. It wasn't clear, for example, whether the NoMatchPedantic option should convert to true or false of if I should even support the current usage rather than make every use check for each condition explicitly.
I will go back and more carefully review the other usages to see what refactoring I need to do.
Thanks, Seth
Here's an updated patch which takes the suggested approach. I did keep the API compatible, so the matchesType's return value for mismatches converts to false and the value for matches and pedantic mismatches converts to true. This way most uses are unchanged and the code only distinguishes between matches and pedantic mismatches in four checks.
<0001-Add-a-format-warning-for-p-with-non-void-args.patch>
|
0001-Add-a-format-warning-for-p-with-non-void-args.patch
Description: Binary data
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits