So hi, welcome to this new session.
I hope you've got a pretty good idea of what flowcharts and solar calls are and how we can represent
our solution to flowcharts.
So it is very important because every landfill flowchart once, then what happens is it becomes very,
very easy for us to for any kind of solution that we want to print in our program into our code.
It becomes much easier.
Because at least we have understood the first part and the second part is going to be how to write that
in C++ or Java or whatever language you are working with.
Okay, good.
So going forward, we will be writing a lot of code.
We will be doing lots of program.
But before we start writing any program, I just want to give you a small introduction on, like, how
exactly these programming languages work.
What exactly is going on?
For example, in case of C++, what exactly is going on?
Generally what happens is so when you will be writing code, you will be writing something.
Let's say you write some find.
Let's say it has something like this.
It is not exactly gold, but let's say I have done something like this.
So I have some value, a some value to be and then I have some way, Lucy, which is the addition of
first to values.
This makes a lot of sense to us, like we can understand what exactly is written, because this is very,
very close to English.
It is very, very close to the language that we are used to.
But what happens with the computer?
So I don't know how many people know about it.
Computer understand only banditti.
It doesn't know what is A, what is B, what is 15?
It doesn't have any idea.
It knows that one one zero one zero one zero.
Something like this pattern will come.
Basically, I have bids coming in and every bid can either be given orders to do it, only understand
binary and nothing else.
OK, fine.
Now I am writing something and I want my computer to run it.
Computer, do this work for me.
We are doing this only.
OK, so what did the software.
What is a program?
Basically we write something and we want our computer to run it.
If someone has made Chrome written millions of lines of code for it.
Finally, there is a computer which is running that code, right?
Finally, all the software is run by computer.
But computer understand only binary.
And if we are forced to write in binary, then sorry, we won't be able to do it.
We will have to do a lot of hard work to write and banditti, and we will never be able to learn coding.
So we want we will write like this.
But computer gets input in some other.
It is a very common problem.
Let's say there are two people.
The NBA to people, whatever language in those beat doesn't know that language and vice versa.
So what we will do, there are two people who want to communicate but doesn't know each other's language.
So what happened?
Generally, a person will be made to sit between these two people.
We call this person a communicator or an interpreter.
So what this interpreter will do for us?
It will take language off.
And we tell me in whatever language we understand and vice versa.
So interpreter converts all you can say, it translates language.
So the language net, we understand, is very, very close to English.
But computer industry and binary.
So basically what we need is before we can run this program on our computer in between, we need a translator.
Translated.
Which will convert our language to computers, language and vice versa.
We call this translator compiler.
Compiler will compile our C++ code and will convert it to binary, which we can finally run on our computer.
OK.
That's what basically a compiler is going to do for us.
It will take this from us and will go out to the computer, which will be binary.
OK, great.
So when you write some code.
This could get comp. first.
So it has to go through a compiler.
And then we get an output file
by Naty Output File.
So this is my code compiler is going to convert my code into binary file, which can be destroyed by
computer.
Compiler not only convert our code, it does one more thing.
It also find mistakes in my code.
Sir, you cannot write like this.
You have to write it like this and all those kinds of mistakes.
So Compiler is going to find all those mistakes for us in this as well.
Okay, so compiler will also find mistakes for us.
OK, so we will come to know about many mistakes at compile time, only these errors are called compile
time errors, some mistakes which the compiler can catch and some mistakes will be there with the compiler
cannot catch.
For example, let's say I have two numbers, A and B, I want to print their product so the output should
be their multiplication.
But I give output as A plus B.
Now, the compiler don't know that I want to print their product, compiler will say, yes, it is valid.
You are adding and addition is valid.
So the compiler will let us do this, but actually we should have multiplied.
So there is a mistake and compiler cannot catch it.
So these types of mistakes will be caught at runtime.
What we will do, we will run our program.
It will run and the output will be different from expected output.
And then we will come to know that we have done a mistake.
So these types of error are called long time errors, runtime errors.
So we will get some errors at compile time and some errors are trending.
OK.
So let us talk about a, b, e.
Some people may be using Guarda blog Sayadi.
Some people will be using their C++ idea and so on.
So what idea?
It does basically it will do all our work.
There will be a play button and very quickly conduct play button.
It will compile and run our program.
So we don't have to compile ourself idea.
We'll compile.
OK, great.
So I will be using God idee throughout this course.
OK.
So let us install cord locks, idee.