fscan: about it

[Pasquale Frega]

Ok, a simple question: can fscan get a simple return with nothing or a
simple escape or anything?
please try this simple code:
#include <stdio.h>;
#include <math.h>;
int main(void) {
int i;
puts("Enter an int number");
fscan("%d", &i);
printf("You have entered: &d\n", i);
}
In this case fgets wait for a number or something from keyboard that
is a string o charter too
if you try to press return with nothing it does not go forward
i hope to has be clean

 

[Ian Collins]

Ok, a simple question: can fscan get a simple return with nothing or a
simple escape or anything?

I assume you meant scanf?

please try this simple code:
#include<stdio.h>;

Don't put a semicolon after an include directive.

#include<math.h>;
int main(void) {
int i;
puts("Enter an int number");
fscan("%d",&i);
printf("You have entered:&d\n", i);
}

You really should post something that compiles.

In this case fgets wait for a number or something from keyboard that
is a string o charter too
if you try to press return with nothing it does not go forward
i hope to has be clean

fgets?

scanf will read until is sees something that isn't white-space or EOF.

You should check the return of (f)scanf, not the value you are trying to
read.

 

[Nick Keighley]

Ok, a simple question: can fscan get a simple return with nothing or a
simple escape or anything?
please try this simple code:
#include <stdio.h>;
#include <math.h>;
int main(void) {
        int i;
        puts("Enter an int number");
        fscan("%d", &i);
        printf("You have entered: &d\n", i);}

In this case fgets wait for a number or something from keyboard that
is a string o charter too
if you try to press return with nothing it does not go forward
i hope to has be clean

are you asking if fscanf() can read a number without a following \n?

As another poster stated, you should post code that compiles.

And you can't follow a #include with a ";"

 

[John Gordon]

Ok, a simple question: can fscan get a simple return with nothing or a
simple escape or anything?

If you want to abort input when the user presses Enter or Escape,
you don't want to use fscanf.

So, the answer is no.

 

[Keith Thompson]

I assume you meant scanf?


Don't put a semicolon after an include directive.


You really should post something that compiles.

With gcc, it compiles with a couple of warnings. By my reading of
6.10.2, an extra semicolon on a #include directive doesn't even violate
a constraint or syntax rule (but it does have undefined behavior).

The typo "&d" for "%d" doesn't even cause undefined behavior; it just
prints the string literal and ignores the second argument.

 

[Ian Collins]

With gcc, it compiles with a couple of warnings. By my reading of
6.10.2, an extra semicolon on a #include directive doesn't even violate
a constraint or syntax rule (but it does have undefined behavior).

The typo "&d" for "%d" doesn't even cause undefined behavior; it just
prints the string literal and ignores the second argument.

c99 /tmp/x.c
"/tmp/x.c", line 1: warning: tokens ignored at end of directive line
"/tmp/x.c", line 2: warning: tokens ignored at end of directive line
"/tmp/x.c", line 6: warning: implicit function declaration: fscan
Undefined first referenced
symbol in file
fscan x.o

So yes, it "compiles", but it certainly won't produce an executable!

 

[Pasquale Frega]

Yesterday I was very tired and I was very sleepy; of course i intend
"scanf" and no "fscan" or "fgets". The code above i have not compiled
so it is not tested as well as i wrote.
I think it is not possible to get by "scanf" something as a simple
return or an f(1-12) or an escape, as well as anyone of you say. The
";" at the end is intend simply as "end" and i use it simply to
improve reading (as well as in Pascal, you might to write always ";").
No other i intend.
Ok, now i formulate the question in other way:
How can i make a program in manner that i can stop it at the prompt
with ESC, in manner that it can reading a simple return, in manner
that i can set function keys to make something, etc..........?
If no with "scanf", what can i use?

 

[James Kuyper]

Yesterday I was very tired and I was very sleepy; of course i intend
"scanf" and no "fscan" or "fgets". The code above i have not compiled
so it is not tested as well as i wrote.
I think it is not possible to get by "scanf" something as a simple
return or an f(1-12) or an escape,

Use the "%c" format to read a single character. If you want it to only
read in a new-line, but to put any other character back into the
read-buffer, then use the scanset feature: "%1[\n]". Using getchar() and
ungetc() is much simpler way to do this, but you did specify that you
wanted to use scanf().

There's no portable way to identify escape sequences and function keys,
but for any given platform you could use "%c" to read in a character at
a time, and then type the keys that you want it to identify, and find
out how they are represented. Keep in mind that some keys may be
represented by multiple characters.

... as well as anyone of you say. The
";" at the end is intend simply as "end" and i use it simply to
improve reading (as well as in Pascal, you might to write always ";").
No other i intend.

There are many places where you can safely insert a ';' without causing
problems - but be careful not put it anywhere where it doesn't belong,
or would change the meaning of your code. However, inserting a ';' in
places where it doesn't make any difference is going to leave people
suspecting that you don't realize that it's not needed, which is going
to make them very worried about your competence as a C programmer. As
long as you're a newbie, I suppose that's not a bad thing, but I'd
recommend dropping the habit. For experienced C programmers, spurious
';' characters do NOT improve reading.

Ok, now i formulate the question in other way:
How can i make a program in manner that i can stop it at the prompt
with ESC, in manner that it can reading a simple return, in manner
that i can set function keys to make something, etc..........?
If no with "scanf", what can i use?

A key problem you need to deal with is buffering. With an unbuffered
stream, as soon as a char becomes available, it can be read by C
character input functions like fgetc(). With line buffering, C input
functions can't retrieve anything until an entire line has been typed
and return has been hit. With full buffering, C input functions do not
see anything until the entire buffer has been filled. C allows full
buffering only if the implementation can be certain that it's not
reading from an input device. Therefore, if stdin is your console, at
worst you're getting line buffering. Unfortunately, what you want is
unbuffered input, and that's not guaranteed - line buffering is much
more common. You can try to make stdin unbuffered by using setbuf(stdin,
NULL), but check for an error return - the standard does not guarantee
that the buffering can be changed. The setbuf() call must occur before
any attempt is made to read from stdin.

 

[Keith Thompson]

The
";" at the end is intend simply as "end" and i use it simply to
improve reading (as well as in Pascal, you might to write always ";").
No other i intend.

A semicolon at the end of a #include directive is not merely useless,
it's wrong. The compiler I use issues a warning and then ignores
it, but other compilers might reject the compilation altogether.

Semicolons in C are not merely decorative. They're part of the
language syntax, and you need to understand where to use them and
where not to use them.

(The same is true in Pascal, by the way.)