Sha256: 6e0f2f8587561887e63024c95f4a7b5643bc8375dd5c6e27860f983f75045c7f
Contents?: true
Size: 1.42 KB
Versions: 328
Compression:
Stored size: 1.42 KB
Contents
## Getting Started Make sure you have read [the C++ page](http://exercism.io/languages/cpp) on exercism.io. This covers the basic information on setting up the development environment expected by the exercises. ## Passing the Tests Get the first test compiling, linking and passing by following the [three rules of test-driven development](http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd). Create just enough structure by declaring namespaces, functions, classes, etc., to satisfy any compiler errors and get the test to fail. Then write just enough code to get the test to pass. Once you've done that, uncomment the next test by moving the following line past the next test. ```C++ #if defined(EXERCISM_RUN_ALL_TESTS) ``` This may result in compile errors as new constructs may be invoked that you haven't yet declared or defined. Again, fix the compile errors minimally to get a failing test, then change the code minimally to pass the test, refactor your implementation for readability and expressiveness and then go on to the next test. Try to use standard C++11 facilities in preference to writing your own low-level algorithms or facilities by hand. [CppReference](http://en.cppreference.com/) is a wiki reference to the C++ language and standard library. If you are new to C++, but have programmed in C, beware of [C traps and pitfalls](http://www.slideshare.net/LegalizeAdulthood/c-traps-and-pitfalls-for-c-programmers).
Version data entries
328 entries across 328 versions & 1 rubygems