🚀 go-pugleaf

I've come across what I believe is a bug in Borland C++.  The following 
program fragment does not work as one would expect.

        scanf("%s", var1);
	gets(var2);

The scanf() statement executes correctly but gets() assigns a null string to 
var2 without waiting for input from the keyboard and execution continues with
the next statment.  If the scanf() is removed, gets() works as advertised.
A work around that I have found is to simply include a dummy call to gets():

	scanf("%s", var1);
	gets(var2);
	gets(var2);

The second call to gets() works correctly.

If a subsequent call to scanf() is made, another dummy call to gets() is
required for gets() to work again.

Has anyone ever come across this before (please e-mail)?

Dan.