Paul Edwards wrote in a message to Phil Crown:

PC> What's the bug in EMX?  I might run across it and not even notice it,
PC> thinking its in *my* code. :-)

 PE> /* According to my interpretation of ISO/IEC 9899:1990, this
 PE>    program should print "2".  It prints "-1"
instead, under
 PE>    EMX 0.9a. */

 PE> #include 

 PE> int main(void)
 PE> {
 PE>     char buf[50] = "5 6";
 PE>     int x, y;
 PE>     int ret;
 PE>     
 PE>     ret = sscanf(buf, "%d %d p", &x, &y);
 PE>     printf("ret is %d\n", ret);
 PE>     return (0);
 PE> }

I think that EMX is behaving correctly.  If 'p' is not matched exactly,
that is a failure of the input stream, and sscanf() should return EOF.

I checked using Borland C and Watcom C, and both return 2.  Reading the
spec document, however, suggests that the proper return is, in fact, EOF.
 
-- Mike


---