- 30 1月, 2018 2 次提交
-
-
由 Jonathan Giszczak 提交于
-
由 Jonathan Giszczak 提交于
-
- 15 11月, 2017 4 次提交
-
-
由 Matias Romeo 提交于
-
由 Matias Romeo 提交于
-
由 Matias Romeo 提交于
Now we use the folder of the header file where the type is defined as the root context. Types declared in header files located in child sub-folders will also be exported. * Code generator now complies with the new coding standard. * Fix contract annotations. * Fix simpledb / Use the generated functions to deserialize/dump messages. * Add optional flag to eoscpp generate-abi command to also generate serialization helper functions for the types defined in the ABI file. * Fix abi_tests.
-
由 Matias Romeo 提交于
-
- 08 11月, 2017 2 次提交
-
-
由 Pravin 提交于
-
由 Brian Johnson 提交于
-
- 30 10月, 2017 2 次提交
-
-
由 Matias Romeo 提交于
* Fix simpledb contract
-
由 Matias Romeo 提交于
Under this approach the functions in simpledb.gen.hpp can be auto-generated using the ABI definition. In particular the specialization for currentMessage must only be defined if the struct has at least one variable length type (String, Bytes, etc), otherwise the default function will do ok. The functions valueToBytes/bytesToValue must only be defined when the table is a KeyValue table. These are required because the underlying db functions receives and returns the serialized version of the value. Then we can simplify the interface for the C++ helper VarTable (maybe reanaming to KeyValueTable?) specifying the KeyType and the ValueType. template<AccountName scope, AccountName code, TableName table, typename KeyType, typename ValueType> struct KeyValueTable and inside the store/load functions (table_impl_obj) we need to call valueToBytes/bytesToValue accordingly. Ref #492
-
- 12 10月, 2017 1 次提交
-
-
由 Andrianto Lie 提交于
-
- 19 9月, 2017 2 次提交
-
-
由 Matias Romeo 提交于
-
由 Matias Romeo 提交于
-
- 28 8月, 2017 1 次提交
-
-
由 Matias Romeo 提交于
-