On Tue, 29 Jun 2010, Earnie wrote:
> Vincent Torri wrote:
>> Your comments are not quite precise, you even don't answer to my question.
> Greg's comments were precise to your post.
"That page says "The h, l, and L prefixes are Microsoft extensions when
used with data of type char.""
So what ? I have given you that web page. I've read it. I have read the
comment, and more importantly, i have read what is in the table, that is
how i should use the modifier. Is Greg's comment useful ? no.
"Then you're using a nonstandard extension."
So what ? I'm using Microsoft extension, for a program that will run on
Windows, compiled with a compiler that should support miscrosoft
extensions. Again, useless.
"And gcc warns that the code is nonstandard."
So what ? (bis). Same remark
> Your question wasn't what do
> I do on Windows using GCC to get the same result as this on Linux. Your
> question was "What did I do wrong" and Greg answered that question by
> telling you to disable the warning if you don't want them.
Did I ask : "What can I do to not have the warning ?" or "that warning is
very annoying, how to not have it ?".
"Am I doing something wrong or is there a bug in header files ?"
A good answer would have been :
No you are not doing something wrong because (put a justification here).
And (yes/no) about header files
Yes you are doing something wring because (put a justification).
What did I get as answer ? :
"If you don't want gcc to give this warning, then inhibit it."
And you say that he correctly replied to my question ? Are you kidding ?
For me, it was trivial that the whole purpose of my mail is : Why is there
such warning, while there shouldn't. For me, there shouldn't be any
warning because sscanf belongs to Microsoft libc, msvcrt*.dll. Hence, the
mingw compiler should respect that. According to msdn, "%hc" is for
unsigned char *. But the mingw compiler warns and say that it should be a
short. As it is VERY important for us to be sure of what sscanf does in
that precise case, i'm trying to understand that warning.