Timeline for Initialize a big fixed length array in Solidity
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2018 at 11:44 | comment | added | Karan | You don't need C. First deploy B. Set values in B. Deploy A with address of B in constructor. call getVector from A, on B's instance. obviously, there are many other way to achieve the same depending on your dapp requirements. | |
| Apr 17, 2018 at 11:40 | comment | added | Karan | Values once pushed to blockchain will remain there forever , and won't change. If you have an exclusive owner editable only function which pushes data from console/js/python, you will achieve what you want. Don't think of it as passing values while deploying the contract. think of it passing value just after deploying the contracts. | |
| Apr 17, 2018 at 10:59 | comment | added | Xaler | Hi ! Thanks for the fast reply. Why you say "can't" and "shouldn't" about hardcoding data structure ? The only way I can think of a graph is specifying nodes (how many) and edges (hardcoded since they are unique for a specific graph). Regarding the hint you gave me: Do you mean passing an hardcoded vector from the console directly to the constructor parameters of my ContractB ? I will create a separate contractC to initializate a contractB with a set function. Then I will use this specific address of contractB inside my contractA constructor. Is this right ? | |
| Apr 17, 2018 at 9:19 | history | answered | Karan | CC BY-SA 3.0 |