BOSCORE/BOS 2.0.2 fixes and EOSIO 1.6.0 & Takeaways

sheldonhuang (50)in #boscore • 6 years ago

This article didnot cover all changes, only insofar the necessary changes that looks imperative for me.

1. New Standard PR in eosio
2. disable max-implicit
3. llvm directory in MacOS
4. Python-dev in C++
5. assert size_t in wasm_interface.cpp
6. boost homebrew mac
7. Types in C++ 
8. LiteralType & trivial destructor

1. new standard PR:

Example PR: https://github.com/EOSIO/eos/pull/6759

Change Desc
Consensus
API 
Documentation

2. `max-implicit-request` is disabled, it used to specific

https://github.com/EOSIO/eos/commit/2edbf2fb84fe66e052d3ae56806ea3bbaf49a315

max sizes of transaction that are sent without first sending a notice

3. llvm macOS

relocated llvm to the correct directory in Apple MacOS Under local/opt/usr/local/opt/llvm@/lib/cmake/llvm Enable auto update by gathering brew files

4. Python-dev in C++

python-dev is the package that contains the header files for the Python C/C++ API,

5. Limit assert size_t = 1024

set in libraries/chain/wasm_interface

constexpr: evaluated the val of variable or function at compiled time

LiteralType

6. Boost brew install

https://github.com/EOSIO/eos/pull/6721/files#diff-597acdcec1b4a1c5cc179fbd43de3e24

7. Types Categories

pointer, member pointer【object, function】, enum, arith【intergral, float】, std::nullptr_t

https://stackoverflow.com/questions/14821936/what-is-a-scalar-object-in-c

reference

pointer, member pointer, enum

Continus: lvalue, rvalue

8. LiteralType

scalar, references, classes, arrays of three before

classes:

Criteria I

trivial destructor
The destructor is not user-provided (meaning, it is either implicitly declared, or explicitly defined as defaulted on its first declaration)
The destructor is not virtual (that is, the base class destructor is not virtual)
All direct base classes have trivial destructors
All non-static members of class type have trivial destructors

Criteria II