Re: [Msys2-users] Weird behaviour with printf() and scanf()

[Andrew L. <ci...@wh...>]

On 13/01/2016 7:08 PM, Paul Moore wrote:
> On 13 January 2016 at 10:57, Andrew Lowe <ci...@wh...> wrote:
>> /* * Activity Name:
[snip]

>> -----------------------------
>>
>> I've compiled this using the latest, as of a week ago, versions of
>> both clang and gcc and the behaviour is the same.
>
> This appears to be a buffering issue. When you write to stdout, the
> data is buffered. You could try adding a fflush(stdout) just before
> your scanf call. See
> http://stackoverflow.com/questions/3723795/is-stdout-line-buffered-unbuffered-or-indeterminate-by-default
>
>
for a discussion.
>
> Paul
>
	Thanks for the thought but that's not going to work. I can't go placing 
more road blocks in front of the students. It's hard enough as it is to 
get them to do/understand what's going on without adding fflush() to the 
mix.

	I just need the same behaviour as cmd.exe and bash under Linux. Is 
there something in Mintty/bash that I can "turn on/off"?

	Andrew