Liste des Groupes | Revenir à theory |
On 2024-05-17 18:24, olcott wrote:Yes and several people also continue to point out that DOn 5/17/2024 6:15 PM, André G. Isaak wrote:You're missing the point. This error had been pointed out to you multiple times by multiple posters. Alan even pointed out the *specific* compiler errors which it generated under GCC. Yet you refused to correct it for weeks on end, insisting that everyone else was wrong.On 2024-05-17 17:00, olcott wrote:>On 5/17/2024 3:02 PM, Alan Mackenzie wrote:>>That "program" doesn't compile. It's ill-formed.>
This does compile under C17 and C11
with Microsoft Visual Studio 2022*Maybe you forgot to take the line numbers out*>
*Maybe you forgot to take the line numbers out*
*Maybe you forgot to take the line numbers out*
*Maybe you forgot to take the line numbers out*
>
typedef int (*ptr)();
int H(ptr P, ptr I);
But that's not the code you provide in your numerous previous posts where you insist on
>
int H(ptr x, ptr x);
>
Maybe when people point out that there is an error you should actually proofread what you wrote.
>
[remaining code deleted].
>
André
>
*Whoops my mistake*
*Whoops my mistake*
*Whoops my mistake*
*Whoops my mistake*
>
Thanks for your review.
>
I couldn't see my mistake when I tried to compile it
so I used an old trick, refactor from working code.
I still didn't see my mistake, yet got it to compile.
A competent C programmer wouldn't have run into this issue since they would have declared the function as something like:The actual names are P and I.
int H(ptr programDescription, ptr programInput); // no silly x and y
Yet you continue to question everyone else's 'C-credentials' when you are the one making very basic errors. That hardly inspires confidence in anything else you might say about C.Several people continue to lie about the execution trace
André
Les messages affichés proviennent d'usenet.