1
00:00:00,060 --> 00:00:03,060
So we have three reporting mechanism with us.

2
00:00:03,090 --> 00:00:11,340
It may be either a print or an internet or a cell, so we'll be comparing and finding out the difference

3
00:00:11,340 --> 00:00:13,350
between them because they are very useful.

4
00:00:13,380 --> 00:00:19,490
OK, and this will give you an ability to choose a specific reporting mechanism in a certain situations,

5
00:00:19,500 --> 00:00:19,720
right?

6
00:00:20,010 --> 00:00:25,170
So the blocked design or hybrid design that will be continuing is this what we have, I think pricing

7
00:00:25,200 --> 00:00:27,420
system where you are concerned about, right?

8
00:00:28,080 --> 00:00:31,620
Then we do need a bitstream and we go to an SDK right here.

9
00:00:31,650 --> 00:00:34,950
We will be considering all the three situation right now.

10
00:00:34,950 --> 00:00:37,020
We may have three situation first.

11
00:00:37,020 --> 00:00:42,960
One is where you want to just sing the constant string to the console, right?

12
00:00:42,960 --> 00:00:45,570
So that is the first situation that we have.

13
00:00:45,720 --> 00:00:46,050
OK.

14
00:00:46,350 --> 00:00:51,450
The second one is where you want to bring the values of a variable and the values that are able could

15
00:00:51,450 --> 00:00:52,830
take as an integer value.

16
00:00:53,010 --> 00:00:54,720
We do not have a three routing number.

17
00:00:55,440 --> 00:00:59,640
We are not expecting a floating number for that specific variable.

18
00:00:59,790 --> 00:01:04,910
Third situation may be where you want to send a floating point numbers on to a console.

19
00:01:04,920 --> 00:01:07,320
So these are the three situation that will be handling.

20
00:01:07,800 --> 00:01:11,250
The first one is where you have a constant string.

21
00:01:12,390 --> 00:01:18,720
Look at this generally include the masses, such as the device initialization is successful or not,

22
00:01:18,720 --> 00:01:19,920
whether we are starting at.

23
00:01:20,580 --> 00:01:27,600
The important message which signify that we require the input from a user so we do not require to pass

24
00:01:27,600 --> 00:01:32,310
any variable value, just a constant string indicating the operation that we are performing.

25
00:01:32,580 --> 00:01:37,230
The second situation may be where you want to bring the values of value, but.

26
00:01:38,380 --> 00:01:38,740
OK.

27
00:01:39,010 --> 00:01:41,050
And that do not consist of a floating point.

28
00:01:41,290 --> 00:01:47,260
This is the second situation that we have where we are expecting the fixed point of values we'll get

29
00:01:47,300 --> 00:01:47,770
from.

30
00:01:49,070 --> 00:01:50,930
That we want to send to a council.

31
00:01:51,200 --> 00:01:56,930
OK, the third situation is where we want to saying the floating point number only to a council.

32
00:01:57,230 --> 00:02:04,220
OK, so what are we going to do is we will be profiling all of this three situation with the three reporting

33
00:02:04,220 --> 00:02:08,610
mechanism that we have and will also be performing a competition between them, right?

34
00:02:08,630 --> 00:02:10,160
So we have a clear picture.

35
00:02:11,210 --> 00:02:13,410
The amount of memory they are consuming, right?

36
00:02:13,410 --> 00:02:20,420
So most important by then, we are designing an email system is to utilize the function, which consume

37
00:02:20,570 --> 00:02:27,430
less amount of memory because we have a limited set of memory available with that memory systems, right?

38
00:02:27,450 --> 00:02:36,920
So if we utilize the least amount of memory for the frequently used function, we could quickly build

39
00:02:36,920 --> 00:02:38,660
a complex applications.

40
00:02:38,700 --> 00:02:39,030
OK?

41
00:02:39,800 --> 00:02:41,870
The limited amount of memory that we have.

42
00:02:41,870 --> 00:02:49,520
So we'll also be considering the amount of an amount of memory that are executable file consumed when

43
00:02:49,520 --> 00:02:54,800
we utilize this three function that is still being different and brain dead right, and to access the

44
00:02:54,800 --> 00:02:58,220
amount of memory that are executable will consume.

45
00:02:58,490 --> 00:03:01,940
We will just go to an SDK folder that we have in our project.

46
00:03:02,360 --> 00:03:09,470
And here we will be analyzing the yearly files which represent executable fight all fire and dice the

47
00:03:09,470 --> 00:03:10,330
application, right?

48
00:03:10,760 --> 00:03:12,940
So let me just go to an SDK.

49
00:03:13,550 --> 00:03:17,300
This is a simple manual template that we've been using from the beginning, right?

50
00:03:17,810 --> 00:03:23,420
So first, let's just send the constant stream onto a console right here.

51
00:03:23,420 --> 00:03:25,640
We already connected and SDK terminal.

52
00:03:25,940 --> 00:03:26,360
OK?

53
00:03:26,570 --> 00:03:33,670
With respect to code so that we could analyze the data on the right.

54
00:03:33,980 --> 00:03:37,810
So first function that we have is print, right?

55
00:03:37,820 --> 00:03:44,390
So print is utilized whenever you want to sing the constant string to the console, OK, you do not

56
00:03:44,390 --> 00:03:48,320
want to send the values of away, but that gives you would proceed with the print.

57
00:03:48,630 --> 00:03:54,260
OK, this only work with the constant stream.

58
00:03:54,350 --> 00:03:54,770
OK.

59
00:03:55,430 --> 00:03:58,600
So print allows us to send a constant string on to other.

60
00:03:58,610 --> 00:04:03,320
So this doesn't allow us to send the value of label to up until this fact.

61
00:04:03,570 --> 00:04:09,770
We will just be saving our code and perform and execution of the code right?

62
00:04:11,040 --> 00:04:14,850
Now, if you analyze a console, you do see a constant stream.

63
00:04:14,880 --> 00:04:22,980
OK, now that specific incident, if you analyze the size of an executable, so it is 184 key, right?

64
00:04:22,990 --> 00:04:27,900
So this is our first value that we are getting with the reporting mechanism.

65
00:04:28,300 --> 00:04:28,530
Right.

66
00:04:28,540 --> 00:04:31,040
So here we are, getting 84, when 84.

67
00:04:31,980 --> 00:04:34,940
The next one will give a try to brain death rate.

68
00:04:34,940 --> 00:04:36,810
So let me just go ahead and.

69
00:04:37,940 --> 00:04:43,880
Try to see archaeology and perform any section of a great to bring different levels to saying constant

70
00:04:43,880 --> 00:04:51,170
string as well as a valuable naval right, so will go ahead and try to again relaunch our debug section.

71
00:04:52,140 --> 00:04:59,070
OK, so you do see, again, a constant string which has been printed by upbringing dysfunction again

72
00:04:59,070 --> 00:05:05,760
in that gives the executable file that we are getting is around 260 to give you right to, we are consuming

73
00:05:05,760 --> 00:05:06,720
far more.

74
00:05:08,400 --> 00:05:12,900
Kilobytes as compared to previous print function, right?

75
00:05:13,290 --> 00:05:19,590
That is, give a try to bring OK, which is specifically written for deciding gossip.

76
00:05:19,620 --> 00:05:23,370
OK, so sell print again, constant string.

77
00:05:23,760 --> 00:05:27,570
And what we could do is we could also add a new line character here.

78
00:05:27,670 --> 00:05:27,960
OK.

79
00:05:29,040 --> 00:05:31,740
So we're lagging relaunch the e-book section.

80
00:05:32,890 --> 00:05:38,120
And if you analyze in a steel key console, you will be able to see a constant stream.

81
00:05:38,140 --> 00:05:44,100
Now if you analyze the amount of memory that we are consuming, is it is it a one nine?

82
00:05:44,540 --> 00:05:44,830
Right?

83
00:05:45,160 --> 00:05:51,250
So whenever you are interested in sending the console string a message conveying certain operation to

84
00:05:51,250 --> 00:05:56,230
end user, you would clearly see the brain is operating in an efficient manner.

85
00:05:56,260 --> 00:06:00,850
Right now, let's try to understand if you want to send the value right.

86
00:06:00,850 --> 00:06:06,130
So if we consider the fixed number that we want to say or a fixed point number?

87
00:06:06,430 --> 00:06:06,790
OK.

88
00:06:06,880 --> 00:06:08,260
This is basically an integer.

89
00:06:08,950 --> 00:06:09,310
OK.

90
00:06:09,640 --> 00:06:12,010
And that is something which we want to send, right?

91
00:06:12,020 --> 00:06:22,690
So if you lazily print off with variable value, OK, and then we will be printing the value in a decimal

92
00:06:22,690 --> 00:06:23,560
format, right?

93
00:06:24,130 --> 00:06:26,170
And let it decide at tempo or here.

94
00:06:26,200 --> 00:06:26,530
Right.

95
00:06:26,980 --> 00:06:32,110
So here now, along with the string, we also are sending the values off of a right.

96
00:06:32,650 --> 00:06:38,560
So we are proceeding with the Zilber and it will be again relaunching our epoch section.

97
00:06:39,010 --> 00:06:39,430
OK.

98
00:06:40,360 --> 00:06:46,690
And now you could see that sticky terminal is displaying the constant string with a variable value,

99
00:06:46,690 --> 00:06:48,430
which is hungry right now.

100
00:06:48,430 --> 00:06:57,210
If you analyze the E.L.F says that we are getting it is around one eighty nine keep you right to a teacher

101
00:06:57,250 --> 00:06:58,660
value, which is constant.

102
00:06:58,720 --> 00:07:01,000
We could get one eighty nine right now.

103
00:07:01,000 --> 00:07:02,790
Print do not support any argument.

104
00:07:02,800 --> 00:07:08,890
So if you just try to add a over here, OK and try to save a whole, you could clearly see that we are

105
00:07:08,890 --> 00:07:16,560
getting an error rate so we could not just supply available vegetable and bring the value on to consult

106
00:07:16,570 --> 00:07:17,160
with the print.

107
00:07:17,170 --> 00:07:17,500
OK?

108
00:07:17,950 --> 00:07:25,390
So here it is not applicable right now if we consider printer, so let it just go ahead and try to add

109
00:07:25,390 --> 00:07:28,690
a printer, so printer to support an argument off label.

110
00:07:28,720 --> 00:07:29,110
OK.

111
00:07:29,620 --> 00:07:34,420
And now if you just try to perform a relaunch session again.

112
00:07:35,530 --> 00:07:37,810
Now you could be able to get the scene.

113
00:07:39,930 --> 00:07:45,000
Message onto a console, as we are getting with resulting in death and the science, which is interesting

114
00:07:45,000 --> 00:07:51,200
point to note, is around 260 to keep OK, which is far greater than I tell think so.

115
00:07:51,210 --> 00:07:55,320
We'll just be adding to 60 to keep right now.

116
00:07:55,620 --> 00:07:56,160
Let it die.

117
00:07:56,160 --> 00:07:59,400
You may want to sing the floating point number eight.

118
00:07:59,400 --> 00:08:04,130
So again, we already know that pink won't be supporting and younger.

119
00:08:04,320 --> 00:08:08,120
So here we are not allowed to use up radar.

120
00:08:08,340 --> 00:08:14,730
In fact, Pink won't be supporting sending the values on to a cancer only competition that we have is

121
00:08:14,730 --> 00:08:18,300
between the children and bring to.

122
00:08:18,900 --> 00:08:21,840
So let's just consider this now to be a float date.

123
00:08:22,170 --> 00:08:26,950
OK, and the value that we want to send is hundred point two three four.

124
00:08:27,060 --> 00:08:27,350
Right.

125
00:08:27,360 --> 00:08:34,200
First, we proceed with brain death, and we do not need to change anything over here because here we

126
00:08:34,200 --> 00:08:41,370
just need to specify if that basically signify we are printing the floating point number, right?

127
00:08:41,460 --> 00:08:46,710
So let me just see you are cool and try to relaunch a simulation.

128
00:08:47,670 --> 00:08:53,180
So you do see the floating point value on a council, OK, with the printer functioning the size of

129
00:08:53,190 --> 00:08:56,670
executable that we are getting is still too 62.

130
00:08:56,730 --> 00:08:57,090
Right.

131
00:08:57,480 --> 00:08:59,880
So 262 or here.

132
00:09:00,270 --> 00:09:06,150
And if we considered silver that OK, you'll be able to see something interesting, so ready to go ahead

133
00:09:06,150 --> 00:09:12,810
and try to add and still brain death and try to relaunch simulation again?

134
00:09:13,790 --> 00:09:18,530
OK, so you could see that children do not bring a floating point number.

135
00:09:18,620 --> 00:09:18,920
Right?

136
00:09:19,220 --> 00:09:24,110
So whenever you are in a situation where you want to send a floating point number on to a consultant,

137
00:09:24,130 --> 00:09:25,930
Brent won't be useful.

138
00:09:26,050 --> 00:09:29,480
Right now, this is again not applicable, right?

139
00:09:30,080 --> 00:09:36,920
So you could see for testing, we could use any of this reporting mechanism either to bring, dev or

140
00:09:36,920 --> 00:09:37,550
bring our.

141
00:09:38,420 --> 00:09:45,890
And from the amount of memory Canadian perspective we could see bring is the most efficient one whenever

142
00:09:45,890 --> 00:09:48,050
you want to send the constant string.

143
00:09:48,260 --> 00:09:54,800
You could also use the printer right when we want to send a fix point number on to a console.

144
00:09:54,800 --> 00:10:01,490
So there we could use the printed and printer print, do not support and arguments.

145
00:10:01,700 --> 00:10:04,580
So bring do not have any provision to add an argument.

146
00:10:04,940 --> 00:10:11,390
So this won't be useful if you want to send the values of a variable to a council so we can either proceed

147
00:10:11,390 --> 00:10:13,550
with helping death or upgrade.

148
00:10:13,730 --> 00:10:18,920
But you could clearly see Zilber interface efficient when compared to printer.

149
00:10:19,430 --> 00:10:25,070
And if you considered the floating point number two XL printer, do not support sending the floating

150
00:10:25,070 --> 00:10:26,270
point number on your console.

151
00:10:26,300 --> 00:10:30,850
Similarly, print do not support and so we are only left with the printer.

152
00:10:30,860 --> 00:10:36,410
So whenever you are in a situation where we want Hussein flirting going, no, go ahead with a printer.

153
00:10:36,680 --> 00:10:42,320
Whenever you want to bring the values of a label with a fixed point number, the most preferred choice

154
00:10:42,320 --> 00:10:43,970
will be to go with the printer.

155
00:10:43,970 --> 00:10:49,160
If, in fact, if you want to saying the constant string to print do not consume much right?

156
00:10:49,790 --> 00:10:57,650
But to find out the most efficient way of sending the constant string is to utilize the print while

157
00:10:57,650 --> 00:10:59,620
sending the message on to ends.

158
00:10:59,810 --> 00:11:00,120
Great.