Timeline for How can eosio.token (v1.4.0) compile?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 14, 2019 at 0:27 | comment | added | ekkis | I guess I'm trying to understand whether the v1.4.0 version of the contracts that the guide uses is later or earlier than the master branch. I guess if it's a branch then it has yet to be merged into master and thus must be more recent. that would mean that the guide expects the latest version of things, which would be a good thing | |
| Jan 12, 2019 at 13:05 | comment | added | conr2d |
@ekkis Do you mean contracts/eosiolib/multi_index.hpp in the master branch of github.com/EOSIO/eos? It was written for eosiocpp (not eosio-cpp) which is old compiler, but now contracts directory in eos repository is used for testing purpose only. contracts directory will be removed in 1.6.0 release and testing would use libraries provided by eosio.cdt repository.
|
|
| Jan 12, 2019 at 0:38 | vote | accept | ekkis | ||
| Jan 11, 2019 at 21:06 | comment | added | ekkis |
actually, that makes sense, if I look in /usr/local/Cellar/eosio.cdt/1.4.1/opt/eosio.cdt/include/eosiolib/multi_index.hpp I see the definition. so that explains why the code compiles. but that brings up another perplexing point: the guide I'm following uses v1.4.0 of the contract, which seems to know about the new same_payer. that would mean it's very current. is 1.4.0 then later than what's on the master branch?
|
|
| Jan 11, 2019 at 20:46 | comment | added | ekkis |
I have 1.4.1 installed (brew info eosio.cdt produces "eosio.cdt: stable 1.4.1 (bottled)")
|
|
| Jan 11, 2019 at 8:38 | history | answered | conr2d | CC BY-SA 4.0 |