WEBVTT 00:00.150 --> 00:06.300 Now, we already looked into how we use a lead me to hide due to a condition that is how we use the 00:06.310 --> 00:06.870 finals. 00:07.200 --> 00:12.070 We'll give you also understood how we can use the multiple coalition in a statement. 00:12.140 --> 00:17.370 To sum up, the good practice that you need to follow is, for example, whenever you are utilizing 00:17.370 --> 00:22.750 a final statement, see that all the coalition, the behavior for all the conditions are specified. 00:22.950 --> 00:27.030 So when we consider the finals, so we have this condition, right? 00:27.030 --> 00:33.000 So when this condition is true, we need to specify the behavior and basically representing what should 00:33.000 --> 00:36.660 be the system behavior when this condition is not true, right? 00:36.870 --> 00:42.720 So this basically represent a complete behavior where we have a condition and we have specified what 00:42.720 --> 00:46.680 should be done when that condition evaluates to true. 00:46.890 --> 00:54.150 We also have specified what should be done when the condition is not evaluated to the right. 00:54.160 --> 00:56.430 So this represents the complete behavior. 00:56.490 --> 01:04.620 Now let's assume if we remove the cells from this, if construct right, so we remove else now this 01:04.620 --> 01:11.370 is what we refer to as an incomplete behavior where we are defining what should be done when the condition 01:11.370 --> 01:12.420 evaluates to true. 01:12.630 --> 01:18.450 But we have not specified what should be done, then this condition do not. 01:18.590 --> 01:19.350 All right. 01:19.350 --> 01:23.130 So this basically leads to the creation of a latch, right? 01:23.340 --> 01:28.030 So Latch are not natively supported by an FPGA. 01:28.050 --> 01:35.820 OK, so that basically restrict our maximum frequency usage and also design the extra circuitry into 01:35.850 --> 01:37.730 our entire design, right? 01:37.740 --> 01:46.710 So it is highly recommended that you correctly specify the complete behavior for your condition, right? 01:46.710 --> 01:49.740 And it will lead to creation of an extra circuitry. 01:49.740 --> 01:55.530 And you may get an unexpected behavior from an implemented rate to with this. 01:55.650 --> 02:02.400 OK, so we already know that when we completely specify the behavior, we are able to invoke always 02:02.400 --> 02:11.580 to one select already display and try to first analyze the behavior we get, then we correctly specify 02:11.580 --> 02:12.540 all the conditions, right? 02:12.540 --> 02:18.450 So here we specified when selected 0Y should be connected to it and else y should be, this should be 02:18.480 --> 02:18.750 right. 02:19.050 --> 02:22.290 Okay, so here we correctly define all the condition, right? 02:22.740 --> 02:29.900 So let me just reload our schematic and analyze the component that is being worked out for this, right? 02:30.360 --> 02:34.380 So if you analyze a schematic, you able to invoke article marks. 02:35.580 --> 02:39.300 OK, two of the inputs are organically connected to an input performance. 02:39.600 --> 02:42.600 And we also have a control input connected to a great time. 02:42.840 --> 02:45.960 The output is also connected to an all fly great. 02:46.200 --> 02:51.510 So this represents the correct component, right, that we want when you walk out of this call. 02:51.750 --> 02:56.570 Now, if you just dream, who else like wants to be right? 02:56.580 --> 02:59.340 So this basically represent an incomplete behavior. 02:59.380 --> 03:05.280 OK, here we do not mention the system behavior when conditions do not evaluate the true right. 03:05.520 --> 03:12.270 And this basically will lead to creation of a large and an extra circuitry OK, resulting into an unpredictable 03:12.270 --> 03:12.740 behavior. 03:12.750 --> 03:20.370 So if you just analyze the schematic after this modification, you could clearly see we have an ideal 03:20.370 --> 03:21.240 max rate. 03:21.930 --> 03:25.830 But Dr. Max is connected to something else, right? 03:25.830 --> 03:29.810 So it is connected to we see over here and here it is connected to a ground. 03:30.300 --> 03:32.140 And then if you analyze this. 03:32.160 --> 03:35.810 OK, so we have one latch which is in there. 03:35.820 --> 03:41.550 It is connected to this deal, but this is not something that we are expecting, right? 03:41.570 --> 03:47.000 So we are expecting a month, but we want to get something which we never expect to make. 03:47.220 --> 03:54.300 So remember, whenever you are utilizing offensively, you must declare the behavior of the system and 03:54.300 --> 03:59.820 condition, evaluate to true and the behavior when conditions do not evaluate you, right?