I'm guessing it's something about buffering , but I'm not sure.
It isn't. Note that you're doing chomp($ans=<STDIN>); in your perl code, while you're not doing anything like that in the C code.
#include <stdio.h> int main() { char answer=' '; printf("(F)irst,(S)econd,(T)hird\n"); scanf("%c",&answer); while(answer !='F' && answer !='S' && answer !='T') { printf("answer was: '%c', which is not what I want\n",answer); printf("(F)irst,(S)econd,(T)hird\n"); scanf("%c",&answer); } return 0; }
Gives:
$ ./a.out (F)irst,(S)econd,(T)hird a answer was: 'a', which is not what I want (F)irst,(S)econd,(T)hird answer was: ' ', which is not what I want (F)irst,(S)econd,(T)hird

In reply to Re: Why does perl get this right and C doesn't ? by Joost
in thread Why does perl get this right and C doesn't ? by Alien

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.