That you could use with a data flow modeling state are listed away.
Right, so we'll just be going through each of them in a detailed OK.
And we'll also be considering an example as we progress, by the way, to a logical operator to include
an AR nine or X are ignoring all the.
Gigs that you that you could find in a designer available with us to whenever you want to use and I
know better, you just need to write and I think you were right, for example, if our system is something
like this, right?
So you have a system, right?
And this consists of simple architecture like this.
So would it be and why?
Right?
So in that case, we'll just be adding way and then E!
And.
So this is how we will be representing this date.
Right?
We have a discourse about an assignment operator yet.
So as we progress further, we will be discussing what are the different assignment operators that we
have with this today.
Similarly, if this system consists of in Aldgate, you could just use an Arquilla nine nor X or ignore
or not.
Right?
Then we have an automatic operator now, in fact.
OK, so that's something that could be used to build a complex circuit with a data flow modeling standard.
So even though if your system consists of just an idea.
OK, so that you could also implement with the help of a little more U.S. data when we are discussing
parliament is what we decided is whenever you have a situation that you replace your system with the
be psychological, then you prefer to go with a little more, let's say.
But if your system can be replaced with the basic automatic block again, that is also we could use
data flow more say so.
This is something that we have added on the top of what we have discussed about data flow.
So if your system is replaced with the basic idea or subtract or multiply, then also you would proceed
with that no one.
So we have added so addition operator is it does.
Then we have an multiplication operator.
We also have a subsection operator, right?
In fact, other than this, we also have some other operator, but they are not good at synthesis,
right?
So if you have a situation for implementing a division, OK, and that is, we need to implement our
own algorithm so that it will be in most of the keys of choice, right?
Instead of utilizing the.
Division operated that we have in, and we did all you could just proceed with and vendor specific APIs
for divide that you'll frequently find in an IP block, right?
So we'll be discussing more on in the division as we progress.
But other than that, we also have a shift obliterates if you want to implement a simple shift operation.
We also have a shift operator with this idea, then that we also have a relational operator.
So when you want to choose whether two numbers are equal or unequal, less than greater than all the
relational operators are also available with it.
Remember, the fundamental concept will remain sim.
That is, whenever we replace the system with the basic logic, OK, we prefer to go with our flow marketing
state.
OK.
But you will just modify that rule a bit.
That is, if we could replace that system, OK with a basic, basic arithmetic block.
OK.
For example, our system just consists of a single I did all single multiplayer.
Then we do have a second operator with us.
Similarly, if a system just consists of one shifter, OK, then in that case also we could implement
it with a data flow modeling state for a relational operator.
We need to understand the assignment operator in detail, and there we will be utilizing the relational
operator, right?
So remember, these are the operators that we have with this.
So even though have no more leaks, still supports automatic shift and relational operators along with
the logical operator.
But my recommendation is then you replace your system with the basic logic gate.
OK, then only you prefer to go with the data flow modeling state forests of the cases we do have and
other models still available.
So instead of unnecessarily confusing us, what we could assume is, OK, these operators are simply
not available.
OK, so what we could do is you miss this operator.
We'll get this operator.
Automatic shift and religion will simply be not using with the flow modeling state, so we will only
be sticking to the logical operator.
OK.
And that quickly simplifies ad logic, right?
Because we do have another modeling state with which we could actually implement the same system.
Right?
So just keep this fact in mind that they do exist.
Medics shift and relational operator along with the logical operator for modeling sake.
But we will be offering 30W morning sale only when we replace our system with a basic logic.
Great.
So in the cases where you're required to have an automatic shipped or relational operator, the good
idea will be that we prefer to go with that behavioral model.
Remember this thing?
So this is just for an information purpose that we have an automatic shift and relational operator been
present in the in our.
Dataflow Malling sale, along with a logical operator, but we will always be preparing to go with only
a logical operator.
So far, the case is very, very where we required an automatic shift or additional operator will be
preparing to go with an either model.
So this will keep our rule unchanged.
That is, we will be utilizing the lead of the morning state only when we replace our system with the
basic logic.