dexon-solidity - DEXON fork of Solidity (https://github.com/dexon-foundation/dsolidity)

	Commit message (Collapse)	Author	Age	Files	Lines
*	Replace cpp-ethereum with solidity in the license headers	Alex Beregszaszi	2017-02-02	1	-4/+4
\|
*	Do not evaluate strings if assertion succeeds.	chriseth	2017-01-13	1	-20/+12
\|
*	Explicitly convert the assert condition using bool()	Yoichi Hirai	2016-09-10	1	-13/+1
\| \| \| \|	This allows a shared pointer as a condition because bool(std::shared_ptr<T>) is defined.
*	Make the Solidity repository standalone.	Bob Summerwill	2016-08-01	1	-0/+111
	This commit is the culmination of several months of work to decouple Solidity from the webthree-umbrella so that it can be developed in parallel with cpp-ethereum (the Ethereum C++ runtime) and so that even for the Solidity unit-tests there is no hard-dependency onto the C++ runtime. The Tests-over-IPC refactoring was a major step in the same process which was already committed. This commit contains the following changes: - A subset of the CMake functionality in webthree-helpers was extracted and tailored for Solidity into ./cmake. Further cleanup is certainly possible. - A subset of the libdevcore functionality in libweb3core was extracted and tailored for Solidity into ./libdevcore. Further cleanup is certainly possible - The gas price constants in EVMSchedule were orphaned into libevmasm. - Some other refactorings and cleanups were made to sever unnecessary EVM dependencies in the Solidity unit-tests. - TravisCI and Appveyor support was added, covering builds and running of the unit-tests (Linux and macOS only for now) - A bug-fix was made to get the Tests-over-IPC running on macOS. - There are still reliability issues in the unit-tests, which need immediate attention. The Travis build has been flipped to run the unit-tests 5 times, to try to flush these out. - The Emscripten automation which was previously in webthree-umbrella was merged into the TravisCI automation here. - The development ZIP deployment step has been commented out, but we will want to read that ONLY for release branch. Further iteration on these changes will definitely be needed, but I feel these have got to sufficient maturity than holding them back further isn't winning us anything. It is go time :-)