I was so confused whule working on a practice problem, and you sir, helped me, not only figure out the solution, but also understand why it is the solution. Thank you bro!
Wow! That's why follow your channel, here I get not only solutions but also the underhood mechanism behind the behavior. Keep up the good work. Thanks for providing such wonderful lectures.
Is possible to use "%d%*c" on scanf format specifier. That will read the number (%d part) and the " ", then will ignore the " " (the * character ignores the matching case and the "c" means a character), this way you dont have to make another function call (fgetc(stdin)) and also use one less line.
thank you very much, I looked for over 20 minutes for a solution to my problem and there was not a single video or webpage that explained the issue, thanks for the 10/10 tutorial
Old languages come with a lot of problems behind the scene. Especially when it comes to common functions such as scanf. If you "fix" this issue in a new version of C, who knows how many other pieces of old code rely on this exact functionality that we think is broken. C and C++ for that matter have always been backwards compatible and these are the kind of issues that remain due to that. It's a similar issue (but much larger) with x86 assembly
@@CodeVault About old languages my favorite is Pascal. I really love programming my personal projects particularly in Free Pascal using Lazarus IDE. To be fair though, Free Pascal is not really an old language, it's surprisingly modern and powerful. But I cannot say that I dislike C because of the above problems mentioned. I like C very much.. it gives me the feeling that I understand what I'm doing. And of course your videos are very helpful, actually they are the best in YT. No exaggeration on this.
Thank you so much, I was so confused on why my fgets function was not executing, but worked completely fine when I moved it at the very start of my main function. Now I know😂
Thank you so much! I was so frustrated on why my code is not working and searched on the web but found nothing. And then I found this video and the way you explained it was so amazing and easy to understand and my code is working! Thank you!
Thanks for the great video. It seems all the input functions ie. getchar(), scanf() getc() etc... use the same input buffer and is why the problem occurs ie. when characters remain in the buffer they are recognized as user input by the next call to scanf() and is the reason they are skipped. In the video was used fgetc() to clear the newline; however, trying getchar() it seems to do the same job.
Yeah, there are many similar functions to fgetc(). There are so many that there's actually a video regarding this: code-vault.net/lesson/t1rx0xlx2e:1603733525238
You said you hope we get something out of this video. I'm telling you as matter of fact that ALL of the videos you put out are beneficial to one degree or another for anyone watching them. I personally noticed very quicly about you that you give some substance in your vieos that many really do not in the 'C' language. It is like they give the same out of the book example. And that doesn't help ppl learn when they are all using the same examples and even simple examples at that. So I definitely appreciate and thank you for not doing that but for giving better quality. I do hope that your viewership and subscriber base increases and does so quickly.
I always have issues with that scanf. But yes, you could use that "%[^ ]s" format in place of the scanf in the video and it should also work fine. Although... I really suggest you just use fgets at that point
Thanks sooo much for your awesome videos, but I keep seeing you say "You can check up on top" where you are pointing upward... but I cannot figure out what "up on top" means. There is more than one C language playlist soooo hard to figure this out. Thank you!
Because you can't seek on console streams (such as stdin) and, technically, it might result in undefined behaviour as it's not specified in standards. Although, yes, that works
fflush(stdin) is not standard, that's why it's not recommended to use it. You can read more on this by others more experienced: stackoverflow.com/questions/2979209/using-fflushstdin
Hi guys, I"m just a newbee when it comes to c howveer when i use fgets() it ommits the first character of my code and prints outn the rest can some one explain or provide resources for me to understand how this works.. Thankyou: char school[30]; printf("enter schools name"); fgets(school, 30, stdin);
I tested the code and it works just fine. What do you mean by "it omits the first character"? Can you give me an example and the code you used to test this?
@@CodeVaultsure char school[80]; printf("Enter the high school you went to: "); fgets(school, sizeof(school), stdin ); printf("the schools is %s",school) oooh sorry, i kind forgot to add the name of the variable in my printf statement
Nobody talked about that problem, only you did that and helped me. Thanks a lot man!
I was so confused whule working on a practice problem, and you sir, helped me, not only figure out the solution, but also understand why it is the solution. Thank you bro!
Wow! That's why follow your channel, here I get not only solutions but also the underhood mechanism behind the behavior. Keep up the good work. Thanks for providing such wonderful lectures.
Your C language tutorial is a very high-quality course. Very effective! Thank's.
Thank you so much for your C tutorials. Pls keep 'em coming!!
You are explaining C language the best on YT. Thx!
Is possible to use "%d%*c" on scanf format specifier. That will read the number (%d part) and the "
", then will ignore the "
" (the * character ignores the matching case and the "c" means a character), this way you dont have to make another function call (fgetc(stdin)) and also use one less line.
Yea, sure... That's a nice way of getting around this issue with scanf!
That doesn't work with string inputs though, only integers
thank you very much, I looked for over 20 minutes for a solution to my problem and there was not a single video or webpage that explained the
issue, thanks for the 10/10 tutorial
You are a life saver. Can't thank you enough !!!!
It's really sad that C is such an old language and yet still they didn't solved this problem. Thanks for another well explained video.
Old languages come with a lot of problems behind the scene. Especially when it comes to common functions such as scanf. If you "fix" this issue in a new version of C, who knows how many other pieces of old code rely on this exact functionality that we think is broken.
C and C++ for that matter have always been backwards compatible and these are the kind of issues that remain due to that. It's a similar issue (but much larger) with x86 assembly
@@CodeVault About old languages my favorite is Pascal. I really love programming my personal projects particularly in Free Pascal using Lazarus IDE. To be fair though, Free Pascal is not really an old language, it's surprisingly modern and powerful. But I cannot say that I dislike C because of the above problems mentioned. I like C very much.. it gives me the feeling that I understand what I'm doing. And of course your videos are very helpful, actually they are the best in YT. No exaggeration on this.
Thank you so much, I was so confused on why my fgets function was not executing, but worked completely fine when I moved it at the very start of my main function. Now I know😂
This was a great explanation, as all your videos are. Thank you!
Thank you so much! I was so frustrated on why my code is not working and searched on the web but found nothing. And then I found this video and the way you explained it was so amazing and easy to understand and my code is working! Thank you!
You are amazing. I have to learn C for an intro to computer systems class and your tutorials have been invaluable for my learning. Thank you!
Thanks a lot, that was a clear and concise explanation :)
thank you very much your videos are like a savior to me
keep going, man!
Mashallah. Your videos are awesome. Keep up the good work brother.
Thanks for the great video. It seems all the input functions ie. getchar(), scanf() getc() etc... use the same input buffer and is why the problem occurs ie. when characters remain in the buffer they are recognized as user input by the next call to scanf() and is the reason they are skipped. In the video was used fgetc() to clear the newline; however, trying getchar() it seems to do the same job.
Yeah, there are many similar functions to fgetc(). There are so many that there's actually a video regarding this: code-vault.net/lesson/t1rx0xlx2e:1603733525238
Man, you are awsome. Thank you for what you do
You helped me, so let me help you with that UA-cam algorithm.
Thanks a lot, I was going crazy
Thank you very much, I was so confused why it does work like that, but you explained everything perfectly
Thanks so much for this video, it helped me a lot with my C programming assignment!
Thank you very much for the simple solution and explanations !
Thank you! Excellent content!
Awesome video as usual
exactly what I needed, Thank you so much!
really useful to me, thank you for your video❤
You said you hope we get something out of this video. I'm telling you as matter of fact that ALL of the videos you put out are beneficial to one degree or another for anyone watching them. I personally noticed very quicly about you that you give some substance in your vieos that many really do not in the 'C' language. It is like they give the same out of the book example. And that doesn't help ppl learn when they are all using the same examples and even simple examples at that.
So I definitely appreciate and thank you for not doing that but for giving better quality.
I do hope that your viewership and subscriber base increases and does so quickly.
Absolutely true, I searched a lot but never found such good explanation in any other video.
Sir, you are great. I searched for this solution for quite some time nothing worked, but fgetc(stdin) did the trick easily!
When I use debian, pointing fgets to /dev/urandom file descriptor would cause kernel panic. Seems like it fixed on newer kernel. I use arch now btw
Good explanation, thank you!
really good video.you earned new subscriber.
thanks, this helps me a lot :D
i send you my rewards from Mexico!!!
This helps a lot tysm bro
I love you man. Thanks
thanks for tutorials thats help me
Deep Knowledge!!! Nice
man you re worth 2 likes from me thank u so much
Amazing content!
Thanks a lot for this
Nice work! Your tutorials have given me inspiration.
Do you think that scanf(“%[^
]s”, message); have a place here?
I always have issues with that scanf. But yes, you could use that "%[^
]s" format in place of the scanf in the video and it should also work fine. Although... I really suggest you just use fgets at that point
Thanks sooo much for your awesome videos, but I keep seeing you say "You can check up on top" where you are pointing upward... but I cannot figure out what "up on top" means. There is more than one C language playlist soooo hard to figure this out. Thank you!
I mean in the top right corner there's a "i" icon that you can click to see videos I link to this video
Thank You.
thank you man.
How about using fflush(stdin); after each use scanf or fgets, v.v... . I think it's more effectively
That would also work, yes. Although it is regarded as undefined behavior: stackoverflow.com/questions/2979209/using-fflushstdin
thank you so much.
Thanks a lot! How do i detect EOF?:)
The return value is dependent on whether or not you've hit EOF: www.cplusplus.com/reference/cstdio/fgets/
Or you can just check with feof
A life lifesaver
Thanks a lot sir
how do you make to run the program run in terminal on vscode using debug?
There are a couple videos regarding vscode here: code-vault.net/lesson/4wy66ezt7u:1610303902122
Thank you 😭
Hmmmm I got a question here, why don't you use rewind (stdin) :0
Because you can't seek on console streams (such as stdin) and, technically, it might result in undefined behaviour as it's not specified in standards. Although, yes, that works
why not use fflush(stdin); u could clear the buffer too.
fflush(stdin) is not standard, that's why it's not recommended to use it. You can read more on this by others more experienced: stackoverflow.com/questions/2979209/using-fflushstdin
can we do the same with gets?
Yes, but gets is vulnerable: code-vault.net/lesson/q2v3wz26zw:1603733525494
what if i use gets() in place of fgets() ......?
Thanks a lot
can we use fgets to read stdin line by line?
Yes, and it's recommended you actually use it in place of scanf
God bless you
thanks!
Hi guys, I"m just a newbee when it comes to c howveer when i use fgets() it ommits the first character of my code and prints outn the rest can some one explain or provide resources for me to understand how this works.. Thankyou:
char school[30];
printf("enter schools name");
fgets(school, 30, stdin);
I tested the code and it works just fine. What do you mean by "it omits the first character"? Can you give me an example and the code you used to test this?
@@CodeVaultsure
char school[80];
printf("Enter the high school you went to:
");
fgets(school, sizeof(school), stdin );
printf("the schools is %s",school)
oooh sorry, i kind forgot to add the name of the variable in my printf statement
Yeah, seems to be working fine. You're using fgets correctly
Wish I watched this before wasting 3 hours.
ty
огонь
the fuck