1 00:00:00,640 --> 00:00:01,610 Hello, welcome back. 2 00:00:01,630 --> 00:00:08,560 In this lesson, we shall talk about free artist types who talk about data types as well as the variable 3 00:00:08,560 --> 00:00:08,980 types. 4 00:00:09,280 --> 00:00:11,560 And these are just these are just. 5 00:00:12,850 --> 00:00:20,120 New nomenclature or naming conventions used in free Archos, they are no like different types from what 6 00:00:20,120 --> 00:00:20,830 we are used to. 7 00:00:21,050 --> 00:00:24,820 And in fact, this very first light describes what I'm talking about. 8 00:00:25,820 --> 00:00:35,360 So Free describes this to underscore type and basically wherever you see take an escort is a 16 bitz 9 00:00:35,360 --> 00:00:42,200 type you into 16 bit or you into 32 bit based on the configuration settings. 10 00:00:42,350 --> 00:00:47,990 And what this means is we can go to our free Arktos Kernell settings and see that, OK, we want it 11 00:00:47,990 --> 00:00:50,960 to be 16 bits or we want it to be 32 bits. 12 00:00:51,650 --> 00:00:55,760 So this ATIC type, it can be you in 16 or you instead of two. 13 00:00:55,760 --> 00:01:00,850 But there's also another data type known as the base type is written like this. 14 00:01:01,340 --> 00:01:03,920 This is a you into 16 bits type. 15 00:01:03,920 --> 00:01:11,780 If you are running a 16 bit architecture such as Atme or EPIK microcontroller on our arm architecture, 16 00:01:11,990 --> 00:01:13,910 the base type is 32 bit. 17 00:01:14,360 --> 00:01:16,450 So this is architecture specific. 18 00:01:16,730 --> 00:01:23,510 So whenever you require a 32 bit data type, you can just see this type underscore T and then you give 19 00:01:23,510 --> 00:01:25,490 the variable name right. 20 00:01:25,710 --> 00:01:27,740 So that Tic-Tac the base type. 21 00:01:28,010 --> 00:01:31,280 OK, now let's see some naming conventions of variables. 22 00:01:32,120 --> 00:01:32,560 Right. 23 00:01:32,870 --> 00:01:37,240 So variables are often prefixed with the AR type. 24 00:01:37,640 --> 00:01:43,460 So whenever you see in three ATA's a variable name, starting with C, this indicate it's a character 25 00:01:43,460 --> 00:01:43,820 type. 26 00:01:44,360 --> 00:01:51,380 Whenever you see a variable name starting with S, it's indicates it's a short type or an unsigned 16 27 00:01:51,380 --> 00:01:55,860 bit type if you see a variable name starting with the letter L.. 28 00:01:56,330 --> 00:01:59,900 This shows that it's assigned 32 bit type or a long type. 29 00:02:01,340 --> 00:02:10,700 And the other variables that start with X and this means they are off base type and any other non-standard 30 00:02:10,700 --> 00:02:11,070 types. 31 00:02:11,090 --> 00:02:17,870 So if we are to declare a structure, for instance, a structure variable would start with X at Task 32 00:02:18,230 --> 00:02:20,990 Hondo, we start with execution style X.. 33 00:02:21,230 --> 00:02:25,940 The reason we are talking about this is so that when are going through the Free Arktos documentation 34 00:02:26,210 --> 00:02:32,330 or source code of the Arktos, can you see these naming conventions and you'll be able to make use of 35 00:02:32,330 --> 00:02:32,570 them. 36 00:02:33,110 --> 00:02:33,600 OK. 37 00:02:33,830 --> 00:02:38,770 And when we see a variable name, start with you, it's indicates this is an unsigned type. 38 00:02:38,990 --> 00:02:41,900 And of course Pointis will start with the letter P. 39 00:02:43,070 --> 00:02:43,550 OK. 40 00:02:46,520 --> 00:02:54,980 Moving on, so let's see the function names, so just like we said, the variables have prefix functions 41 00:02:54,980 --> 00:03:00,980 also have prefix functions are prefixed with both that type they return and therefore they are defined 42 00:03:00,980 --> 00:03:01,380 within. 43 00:03:01,970 --> 00:03:06,530 For example, we have this function v task priority prioritises. 44 00:03:07,220 --> 00:03:14,870 This returns a void type, hence the letter V this the type it retains and is defined within the task 45 00:03:15,110 --> 00:03:17,390 C as the named task. 46 00:03:17,930 --> 00:03:22,580 So it's first prefixed with the type it's retains in this case void. 47 00:03:22,910 --> 00:03:25,640 And then the second word is the following, which we find it. 48 00:03:25,790 --> 00:03:27,170 We find this in the task. 49 00:03:27,200 --> 00:03:36,920 Doxey file as Task C over here we have this other example X you receive this returns a variable off 50 00:03:36,920 --> 00:03:37,560 base type. 51 00:03:37,580 --> 00:03:45,230 Remember we said base type is the prefix X and we find this in the kudasai file is the next word is 52 00:03:45,230 --> 00:03:48,620 Q of course these functions will use them in the course. 53 00:03:48,950 --> 00:03:51,340 OK, and then we have this other function. 54 00:03:51,620 --> 00:03:54,350 This one has two letters as a prefix. 55 00:03:54,470 --> 00:03:58,400 We have Peevey time to get time ID. 56 00:03:58,640 --> 00:04:06,040 This returns a pointer to avoid his Peevey pointer to avoid and is defined in the time as those cifas 57 00:04:06,680 --> 00:04:08,720 OK as we have this. 58 00:04:08,720 --> 00:04:14,900 So you should, you would be seeing a lot of this as we used if we are to call APIs. 59 00:04:15,630 --> 00:04:18,650 OK, so this order is for this lesson. 60 00:04:19,040 --> 00:04:20,140 I've seen the next lesson. 61 00:04:20,150 --> 00:04:20,840 Have a nice day.