53 lines
2.3 KiB
Markdown
53 lines
2.3 KiB
Markdown
# Robot Name
|
|
|
|
Write a program that manages robot factory settings.
|
|
|
|
When robots come off the factory floor, they have no name.
|
|
|
|
The first time you boot them up, a random name is generated, such as
|
|
RX837 or BC811.
|
|
|
|
Every once in a while we need to reset a robot to its factory settings,
|
|
which means that their name gets wiped. The next time you ask, it will
|
|
respond with a new random name.
|
|
|
|
The names must be random: they should not follow a predictable sequence.
|
|
Random names means a risk of collisions. Your solution should not allow
|
|
the use of the same name twice when avoidable. In some exercism language
|
|
tracks there are tests to ensure that the same name is never used twice.
|
|
|
|
## Getting Started
|
|
|
|
Make sure you have read the [getting started with C++](http://help.exercism.io/getting-started-with-cpp.html)
|
|
page on the [exercism help site](http://help.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).
|
|
|
|
## Source
|
|
|
|
A debugging session with Paul Blackwell at gSchool. [view source](http://gschool.it)
|