sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-25 20:12:57 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
15ca483893
dash/doc
History
MarcoFalke e5b434d411 Merge #12982: Fix inconsistent namespace formatting guidelines 
cd0e1e91dd Fix inconsistent namespace formatting guidelines (Russell Yanofsky)

Pull request description:

  Suggested formatting for namespaces in the developer guide is currently inconsistent. This commit updates the developer guide and clang-format configuration to consistently put "namespace" and opening/closing braces on the same line. Example:

  ```c++
  namespace boost {
  namespace signals2 {
  class connection;
  } // namespace signals2
  } // namespace boost
  ```

  Currently the [Source code organization](https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md#source-code-organization) section has an example like the one above, but the [Coding style](https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md#coding-style) section example and description put a newline between the opening "namespace foo" and brace (but oddly no newline between closing namespace and brace).

  Avoiding newlines before namespace opening braces makes nested declarations less verbose and also avoids asymmetry with closing braces. It's also a common style used in our own and other codebases:

  * https://google.github.io/styleguide/cppguide.html#Namespaces
  * https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style#Classes
  * https://llvm.org/docs/CodingStandards.html#namespace-indentation

Tree-SHA512: 507259478e1a7f6f96db386dd04eb25aa04294f533503fdd82368cf809c3ceaa20204b2cb6ae65322eb27446e5934c1aa1ccb6240ead12aa06b314af76f68139
2020-06-27 10:43:32 -05:00
..
gitian-building Merge #10968: Add instructions for parallel gitian builds. 2019-08-12 09:07:03 -05:00
man Bump develop 0.17 (#3512) 2020-06-11 11:34:42 +03:00
release-notes/dash v0.15 release notes draft (#3283) 2020-01-14 22:46:02 +03:00
.gitignore Merge #10166: Ignore Doxyfile generated from Doxyfile.in template. 2019-05-19 20:43:00 -05:00
assets-attribution.md
benchmarking.md bench_bitcoin -> bench_dash 2020-04-06 16:56:32 +00:00
bips.md Merge #12143: [Doc] Fix link for BIP-159 pull request 2020-06-18 11:41:53 -05:00
bitcoin_logo_doxygen.png
build-cross.md Update Windows build instructions (#3453) 2020-04-30 13:28:12 +03:00
build-generic.md Fix Dash specific docs and scripts 2019-11-04 13:29:32 +01:00
build-osx.md Drop --c++11 brew flag in build-osx.md (#2755) 2019-03-11 11:16:28 +03:00
build-unix.md Update OpenBSD build docs as in bitcoin#11442 2019-09-30 08:33:16 +02:00
build-windows.md Update Windows build instructions (#3453) 2020-04-30 13:28:12 +03:00
developer-notes.md Merge #12982: Fix inconsistent namespace formatting guidelines 2020-06-27 10:43:32 -05:00
dnsseed-policy.md Update dnsseed-policy.md (#2751) 2019-03-08 21:21:20 +03:00
Doxyfile.in Merge #10155: build: Deduplicate version numbers 2019-06-14 01:25:59 -05:00
files.md Merge #11726: Cleanups + nit fixes for walletdir PR 2020-03-04 10:13:19 -06:00
fuzzing.md dashify what made sense in fuzzing.md 2019-08-26 17:25:02 -05:00
gitian-building.md Merge #11392: Fix stale link in gitian-building.md 2020-01-10 10:34:01 -06:00
init.md Merge #10878: Docs: Fix Markdown formatting issues in init.md 2020-01-01 21:33:12 -06:00
instantsend.md Report instantlock: true for transactions locked via ChainLocks (#2877) 2019-04-25 18:38:26 +03:00
keepass.md Update links and references to current communication channels (#1906) 2018-02-08 08:44:21 +03:00
masternode-budget.md Remove all legacy/compatibility MN code (#2600) 2019-01-03 12:17:43 +03:00
README_osx.md
README_windows.txt Merge #10155: build: Deduplicate version numbers 2019-06-14 01:25:59 -05:00
README.md Merge #9172: Resurrect pstratem's "Simple fuzzing framework" 2019-08-24 10:22:40 -05:00
reduce-traffic.md
release-notes.md bitcoin -> Dash Core 2020-04-23 14:33:31 -05:00
release-process.md Merge #12619: doc: Give hint about gitian not able to download 2020-06-18 11:41:53 -05:00
REST-interface.md Few fixes in docs/comments (#3068) 2019-08-28 10:54:19 +03:00
shared-libraries.md Merge #8848: Add NULLDUMMY verify flag in bitcoinconsensus.h 2018-01-30 20:28:51 +01:00
tor.md Merge #12384: [Docs] Add version footnote to tor.md (#3473) 2020-05-12 02:32:38 +03:00
translation_process.md Update links and references to current communication channels (#1906) 2018-02-08 08:44:21 +03:00
translation_strings_policy.md Translations201804 (#2012) 2018-04-30 01:10:20 +03:00
travis-ci.md Merge #8879: [doc] Rework docs 2018-01-12 09:57:56 +01:00
zmq.md Some Dashification (#3513) 2020-06-11 11:39:04 +03:00

README.md

Dash Core

This is the official reference wallet for Dash digital currency and comprises the backbone of the Dash peer-to-peer network. You can download Dash Core or build it yourself using the guides below.

Running

The following are some helpful notes on how to run Dash on your native platform.

Unix

Unpack the files into a directory and run:

  • bin/dash-qt (GUI) or
  • bin/dashd (headless)

Windows

Unpack the files into a directory, and then run dash-qt.exe.

OS X

Drag Dash-Qt to your applications folder, and then run Dash-Qt.

Need Help?

Building

The following are developer notes on how to build Dash Core on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.

Development

The Dash Core repo's root README contains relevant information on the development process and automated testing.

Resources

Miscellaneous

License

Distributed under the MIT software license. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com), and UPnP software written by Thomas Bernard.