C Programming Tutorial 9 - C Basics Part 1 - Variables, Expressions, Statements

[@codebreakthrough]

Learn Javascript - bit.ly/JavaScriptPlaylist Learn Java - bit.ly/JavaPlaylist Learn C# - bit.ly/CSharpTutorialsPlaylist Learn C++ - bit.ly/CPlusPlusPlaylist Learn C - bit.ly/CTutorialsPlaylist

[@happyman1838]

Caleb Curry Kindly clarify this for me %d always saw it in c language

[@burpeeslurpy]

You really broke that down to a level that I can understand. Thanks man

[@herowarner8153]

Can we just acknowledge how hard Caleb works on these videos? Its iNcRedIbLE! In the being of the video it was 6pm, and the end it was 8pm. It took TWO WHOLE HOURS for him to make a seven minute one. If thats not dedication, I don't know what it is.

[@saidmcheni4945]

wasnt six before

[@Skirmish_Master]

It literally took him 7:12 minutes

[@cw4608]

Yes, all the people behind quality videos have invested a great deal of time, expertise, and effort. Caleb is so young, knowledgeable, and prolific it is absolutely amazing to me. He is remarkable.

[@PunmasterSTP]

Caleb might have talked about variables in this tutorial, but there is one thing that isn't variable: the high quality of his videos. On the contrary, it seems constant. Thanks again for making and sharing these things!

[@johnson554671]

Thank you Caleb for your tutorials. I thought you only had tutorials on SQL, but glad to see other tutorials. Very intelligent young man. 0:18 And of course I can remember the structure layout in my head, every programmer should.

[@googlegoogle-uc8ge]

I don't know that much about programming but damn, this guy seems pretty good.

[@sebastianramadan8393]

As I wrote in my own comment, "I think we all expect that people who assume the role of teachers will put countless hours into planning and revising their lessons to avoid inaccurate statements"... It's an expectation, but do you know enough about C to judge that for yourself? I do... and to be frank, I could do a better job than this guy of teaching C, but I won't bother because for less than $50 you can buy a book which does a better job than both of us. Some of us are humble enough to realise, the wheel doesn't need to be reinvented just for the sake of having our names propped up on a pedestal.

[@PunmasterSTP]

@@sebastianramadan8393 I've coded and read books about C before, but I appreciate seeing things demonstrated on a screen, especially with a bit of humor thrown in. I also appreciate how Caleb's tutorials (and others on KZbin) aren't even $50; they're completely free. If people find a resource they like better, then they can just as easily stop watching these videos with no penalty whatsoever.

[@codingmaster6321]

there are two types of programmers : 1. int main(){ } 2. int main() { } : )

[@ilyasofficial1617]

3. int main() { }

[@sebastianramadan8393]

In C programming, `int main()` declares a `main` function which accepts an indeterminate number of arguments (and of indeterminate types), thus is usually an error. See for yourself: `int main() { main("what", "the", "hell", "is", "this?"); }`. I think you meant to write `int main(void)` in both cases. That means something subtly different.

[@garibanibizzeka]

Type 1 here to report

[@caleb22lr]

i came from javascript so i int main() { }

[@helicopter-xj1qr]

@@caleb22lr i came from Java so i do this too: int main() { }

[@happygimp0]

You should use -Wall -Wextra -Wpedantic when you compile C code with GCC. It generates more warnings which can help you eliminating bugs.

[@kayp9318]

I love the giggles btw! Keep being you

[@srajesh2166]

caleb you are notes are good .Iam getting to know every detail about linux commands .Really it helped me a lot.

[@liluna6731]

Caleb, excellent knowledge extending to your viewers. We thank-you. Truly.

[@kayp9318]

Dude you ROCK!! Thank you so much for breaking down in these baby steps. God Bless you!

[@titaniumdiveknife]

short, sharp, and sweet. bravo

[@caleb22lr]

i love your tutorials during quarantine

[@squideronipepperoni]

When he declared the x value, why did he write it as int x; x=10 but then when he declared y he skips the first semicolon? Does that make a difference at all? Could he have just written int x =10; ?

[@CosmosKnight31]

I can't get past the as my system is saying that "No such file or directory compilation terminated."

[@rayplante9643]

@Afzar Nasoordeen I hope they do by now XD

[@julianmoretti7847]

Is there a way to just memorize syntax. Cuz where 99% fail on the logic, I fail on the syntax.

[@chronicsnail6675]

practice, practice, practice

[@stratixfinance]

Reaaaaly good and understandable thank you. You are the best

[@Headcator]

What is the different between "arguments" and "expressions"?

[@fatyeet6882]

Marvelous vid, left a like and a sub =D

[@Varshini-gk2if]

Which software u are using to execute c programs

[@carlitodidthat]

What was the point of the previous unix linux videos?

[@phoenix2464]

are you planing on making a low level c programming tutorial ? i know this is not the appropriate place to ask, as this is a tutorial for beginners

[@codebreakthrough]

Hi! I'm hoping to in the future, but I can't make any promises! After this C series is over, we will see what happens next. :)

[@sebastianramadan8393]

C isn't a low-level language, at least not in any academic use of the term "low-level". It's a portable programming language for Unix which has a somewhat relaxed (and thus subtly dangerous) treatment of errors (allowing for non-portable extentions which aren't technically C and may seem to give C a false "low-level" feeling). Let us be clear on something here: machine code is low-level. C is source code. We use a compiler to compile C to machine code. C thus requires translation to a low-level language. Furthermore, C allows complex abstractions and expressions which low-level programming languages, by definition, do not. For example, you can combine multiple complex expressions into one expression in C, ad-infinitum, where-as in low-level languages you can't, at least by the academic definition set by SICP, the C standard and so forth... See also SICP (which describes high-level languages: "These languages have means of combination and abstraction, such as procedure definition, that are appropriate to the larger-scale organization of systems." -- < web.mit.edu/alexmv/6.037/sicp.pdf >) and the C standard which describes C in the context of an "abstract machine" (and you can't have a concrete "low-level" language for an "abstract" high-level machine).

[@IznaNAhmad]

Are notes for this course still available? The link is not working anymore.

[@b-delapenagabrieladenisemo3455]

THANK YOU SO MUCH 🥰

[@bALDbOY85]

Really good but don't use int main(), thats outdated. Use int main(void) because with int main(void) you are saying it can be called without a parameter.

[@dogbrosinc6912]

Finally understand something

[@JAdamsJr77]

Keep up the good work thanks a lot, your work will be well known to many people just stay at it and don't give up...

[@codebreakthrough]

Thank you so much for the nice comment. :)

[@fivesix3868]

I pray and hope so, too! :)

[@delibarategariwa8037]

Thanks Cal

[@xyrj-x4u]

Amazing！

[@londonsystem6622]

The Best

[@atfarhanwd]

integers are not whole numbers they are integers I mean the Z set , whole numbers are W.

[@THARIQ456]

Are there any people here having a problem with downloading the video notes? Coz, I've tried to insert my emails several times but the 'Submit' button from his website doesn't seem to work properly. If any of you have solutions for this, It'll be very much appreciated. Thanks!

[@codebreakthrough]

The notes should have been fixed... sorry for inconvenience. Care to try again please?

[@THARIQ456]

Hi! Thanks for the quick response. I got the notes now, thanks :)

[@it_designer]

Thank knowledge

[@ash-lo2dc]

Use a ide nano is painful

[@hritiktheopgamer4122]

i dont like math

[@nickhopwood4233]

Wait so what's a statement?

[@nickhopwood4233]

nevermind found it in video 5

[@sebastianramadan8393]

Did you know, `main` is the only function returning `int` that you don't have to write `return 0;` for. It's in the C standard, so you don't have to take my word, you can see for yourself: < port70.net/~nsz/c/c11/n1570.html#5.1.2.2.3 >... Let's just clarify that, I understand if you don't trust me, since there are a lot of people PRETENDING they know C when they really don't. It's a requirement from the standard... and the standard is something all tradespersons follow, right? Each trade has a standard; plumbing, electrical work, cooking and farming all have standards, so does C programming. As with all standards, it's developed by a central standards organisation, the ISO organisation in this case. The compilers we use, they're developed to the standard too. You can research that using Google and gcc manuals if you don't trust that I've linked you to a legitimate copy of the standard. In fact, I encourage and EXPECT that you will read manuals. As a C programmer, it's a requirement in the workplace, so you should get into the habit. Don't trust me; read the manuals and so forth to validate or invalidate what I write, or use dangerous guesswork... Where `int fubar(void) { }` would trigger a warning or error, `int main(void) { }` will not. There's your dangerous guesswork, as supported by the C standard. You state that C is "space-insensitive" here, and then go on to demonstrate that by inserting newlines into some places, but I think you perhaps have barely understood (or perhaps misunderstood) C with respect to this. What happens if you put the newline between `#include` and ``? I put it to you that whitespace is as contextual in C as it is in most programming languages; the exceptions perhaps are python and Haskell, which have enforced scope using whitespace. There are some places where you can't put whitespaces, or where inserting whitespaces changes the meaning of a program. Spaces have meaning depending on the context in a C program. C is NOT "space-insensitive"; it's as "space sensitive" as most languages. I'm going to break off here and form a second comment, because I have something important to discuss with you.

[@sebastianramadan8393]

"A variable is something that can store some data"... I think we all expect that people who assume the role of teachers will put countless hours into planning and revising their lessons to avoid inaccurate statements like this. In the world of general procedural programming, perhaps this loose definition is good enough for a beginner programmer, but you're teaching C. In C, we have this function `bsearch`, which is a part of the standard library, referenced in ``. Here's the manual for that: < pubs.opengroup.org/onlinepubs/9699919799/functions/bsearch.html >. What I want to draw your attention to, and understand as this is the language you're teaching, is the "variable" that the last argument declares... `int (*compar)(const void *, const void *)`

[@titaniumdiveknife]

oy vey

[@tomzhu8719]

int y;