solidity related question of lesson-9 #2312
-
|
We have mentioned Or what happens when we've
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
The place where you initialize each variable determines when the initialization code will run. During initialization the code is executed in the following order:
If the initialization of each variable is independent, this makes no practical difference. You might simply get bytecode that is functionally equivalent but has some instructions ordered slightly differently. If variables depend on each other, you might actually get different results. In all of these places you can refer to other state variables and call arbitrary functions (even external ones). The function you call can have side-effects or modify state variables (even before they are initialized). To avoid problems that can arise from this it's best to keep things simple. Avoid dependencies and for declarations and base constructor arguments try to only use simple constants or functions that do not read or write other state variables. If you need to do something more complex, keep that logic inside the constructor body to make it easier to reason about what runs in what order. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks MAN. |
Beta Was this translation helpful? Give feedback.
-
|
@MasterofBlockchain there is little difference whatsoever if you initialize the variable with its value as a state variable compared to using the constructor to set the value. The slight difference comes with the little dynamic nature of setting the entranceFee value in our deploy script. Passing the value through the constructor make it slightly dynamic that we can easily change the value rather than tampering with the contract code any time there is a change. |
Beta Was this translation helpful? Give feedback.
-
|
Confused about the above statement. It says We can easily change the value of a constructor but can't temper the code? Does that mean If we want to change And I understand when we deploy a contract at the time of deploying we have to enter the fee in the |
Beta Was this translation helpful? Give feedback.
-
|
@MasterofBlockchain Everything I have said above about changing the value applies to when we are in development and testing like you are now. By slightly dynamic, I meant that we can change the value in our deploy scripts when in development instead of changing it in the contract and recompiling again. Once we have finished developing and we have deployed, the value is fixed till the end of time. |
Beta Was this translation helpful? Give feedback.
-
|
You are a True Gem my friend. You have good amount of Patience. Sometime I wonder you would not want to explain me this much. But everytime you come up with a good explanation which helps me to learn and gives motivation of keep going. I truly appreciate all the Efforts you take to write in a easy way. Thank you is not enough but still thanking you. Haha :) |
Beta Was this translation helpful? Give feedback.
-
|
I'm really glad I make your learning journey easier. |
Beta Was this translation helpful? Give feedback.
@MasterofBlockchain there is little difference whatsoever if you initialize the variable with its value as a state variable compared to using the constructor to set the value. The slight difference comes with the little dynamic nature of setting the entranceFee value in our deploy script. Passing the value through the constructor make it slightly dynamic that we can easily change the value rather than tampering with the contract code any time there is a change.
However, it is also important to note that once the contract has been deployed we can't change anything even the entranceFee so it is just a matter of the developer's prefences. If you feel like you will set the fee to a specific v…