So we have three reporting mechanism with us.
It may be either a print or an internet or a cell, so we'll be comparing and finding out the difference
between them because they are very useful.
OK, and this will give you an ability to choose a specific reporting mechanism in a certain situations,
right?
So the blocked design or hybrid design that will be continuing is this what we have, I think pricing
system where you are concerned about, right?
Then we do need a bitstream and we go to an SDK right here.
We will be considering all the three situation right now.
We may have three situation first.
One is where you want to just sing the constant string to the console, right?
So that is the first situation that we have.
OK.
The second one is where you want to bring the values of a variable and the values that are able could
take as an integer value.
We do not have a three routing number.
We are not expecting a floating number for that specific variable.
Third situation may be where you want to send a floating point numbers on to a console.
So these are the three situation that will be handling.
The first one is where you have a constant string.
Look at this generally include the masses, such as the device initialization is successful or not,
whether we are starting at.
The important message which signify that we require the input from a user so we do not require to pass
any variable value, just a constant string indicating the operation that we are performing.
The second situation may be where you want to bring the values of value, but.
OK.
And that do not consist of a floating point.
This is the second situation that we have where we are expecting the fixed point of values we'll get
from.
That we want to send to a council.
OK, the third situation is where we want to saying the floating point number only to a council.
OK, so what are we going to do is we will be profiling all of this three situation with the three reporting
mechanism that we have and will also be performing a competition between them, right?
So we have a clear picture.
The amount of memory they are consuming, right?
So most important by then, we are designing an email system is to utilize the function, which consume
less amount of memory because we have a limited set of memory available with that memory systems, right?
So if we utilize the least amount of memory for the frequently used function, we could quickly build
a complex applications.
OK?
The limited amount of memory that we have.
So we'll also be considering the amount of an amount of memory that are executable file consumed when
we utilize this three function that is still being different and brain dead right, and to access the
amount of memory that are executable will consume.
We will just go to an SDK folder that we have in our project.
And here we will be analyzing the yearly files which represent executable fight all fire and dice the
application, right?
So let me just go to an SDK.
This is a simple manual template that we've been using from the beginning, right?
So first, let's just send the constant stream onto a console right here.
We already connected and SDK terminal.
OK?
With respect to code so that we could analyze the data on the right.
So first function that we have is print, right?
So print is utilized whenever you want to sing the constant string to the console, OK, you do not
want to send the values of away, but that gives you would proceed with the print.
OK, this only work with the constant stream.
OK.
So print allows us to send a constant string on to other.
So this doesn't allow us to send the value of label to up until this fact.
We will just be saving our code and perform and execution of the code right?
Now, if you analyze a console, you do see a constant stream.
OK, now that specific incident, if you analyze the size of an executable, so it is 184 key, right?
So this is our first value that we are getting with the reporting mechanism.
Right.
So here we are, getting 84, when 84.
The next one will give a try to brain death rate.
So let me just go ahead and.
Try to see archaeology and perform any section of a great to bring different levels to saying constant
string as well as a valuable naval right, so will go ahead and try to again relaunch our debug section.
OK, so you do see, again, a constant string which has been printed by upbringing dysfunction again
in that gives the executable file that we are getting is around 260 to give you right to, we are consuming
far more.
Kilobytes as compared to previous print function, right?
That is, give a try to bring OK, which is specifically written for deciding gossip.
OK, so sell print again, constant string.
And what we could do is we could also add a new line character here.
OK.
So we're lagging relaunch the e-book section.
And if you analyze in a steel key console, you will be able to see a constant stream.
Now if you analyze the amount of memory that we are consuming, is it is it a one nine?
Right?
So whenever you are interested in sending the console string a message conveying certain operation to
end user, you would clearly see the brain is operating in an efficient manner.
Right now, let's try to understand if you want to send the value right.
So if we consider the fixed number that we want to say or a fixed point number?
OK.
This is basically an integer.
OK.
And that is something which we want to send, right?
So if you lazily print off with variable value, OK, and then we will be printing the value in a decimal
format, right?
And let it decide at tempo or here.
Right.
So here now, along with the string, we also are sending the values off of a right.
So we are proceeding with the Zilber and it will be again relaunching our epoch section.
OK.
And now you could see that sticky terminal is displaying the constant string with a variable value,
which is hungry right now.
If you analyze the E.L.F says that we are getting it is around one eighty nine keep you right to a teacher
value, which is constant.
We could get one eighty nine right now.
Print do not support any argument.
So if you just try to add a over here, OK and try to save a whole, you could clearly see that we are
getting an error rate so we could not just supply available vegetable and bring the value on to consult
with the print.
OK?
So here it is not applicable right now if we consider printer, so let it just go ahead and try to add
a printer, so printer to support an argument off label.
OK.
And now if you just try to perform a relaunch session again.
Now you could be able to get the scene.
Message onto a console, as we are getting with resulting in death and the science, which is interesting
point to note, is around 260 to keep OK, which is far greater than I tell think so.
We'll just be adding to 60 to keep right now.
Let it die.
You may want to sing the floating point number eight.
So again, we already know that pink won't be supporting and younger.
So here we are not allowed to use up radar.
In fact, Pink won't be supporting sending the values on to a cancer only competition that we have is
between the children and bring to.
So let's just consider this now to be a float date.
OK, and the value that we want to send is hundred point two three four.
Right.
First, we proceed with brain death, and we do not need to change anything over here because here we
just need to specify if that basically signify we are printing the floating point number, right?
So let me just see you are cool and try to relaunch a simulation.
So you do see the floating point value on a council, OK, with the printer functioning the size of
executable that we are getting is still too 62.
Right.
So 262 or here.
And if we considered silver that OK, you'll be able to see something interesting, so ready to go ahead
and try to add and still brain death and try to relaunch simulation again?
OK, so you could see that children do not bring a floating point number.
Right?
So whenever you are in a situation where you want to send a floating point number on to a consultant,
Brent won't be useful.
Right now, this is again not applicable, right?
So you could see for testing, we could use any of this reporting mechanism either to bring, dev or
bring our.
And from the amount of memory Canadian perspective we could see bring is the most efficient one whenever
you want to send the constant string.
You could also use the printer right when we want to send a fix point number on to a console.
So there we could use the printed and printer print, do not support and arguments.
So bring do not have any provision to add an argument.
So this won't be useful if you want to send the values of a variable to a council so we can either proceed
with helping death or upgrade.
But you could clearly see Zilber interface efficient when compared to printer.
And if you considered the floating point number two XL printer, do not support sending the floating
point number on your console.
Similarly, print do not support and so we are only left with the printer.
So whenever you are in a situation where we want Hussein flirting going, no, go ahead with a printer.
Whenever you want to bring the values of a label with a fixed point number, the most preferred choice
will be to go with the printer.
If, in fact, if you want to saying the constant string to print do not consume much right?
But to find out the most efficient way of sending the constant string is to utilize the print while
sending the message on to ends.
Great.