In the new version of eosio we declare the constructor as :
addressbook(name receiver, name code, datastream<const char *> ds) : contract(receiver, code, ds){}
How does datastream
ds work here and what is the meaning of receiver?
EOS.IO Stack Exchange is a question and answer site for users and developers of distributed applications built on top of the blockchain operating system, EOS.IO. It only takes a minute to sign up.
Sign up to join this communityA little late, but this may help people in the future. I know that the receiver is the contract that receives an action, and code is the account that owns the contract that is being executed during the initial action. I am guessing the datastream ds has to do with serialization and deserialization of data from the contract.