67 lines
2.5 KiB
Markdown
67 lines
2.5 KiB
Markdown
|
# Bob
|
||
|
|
|
||
|
|
Bob is a lackadaisical teenager. In conversation, his responses are very limited.
|
||
|
|
|
||
|
|
Bob answers 'Sure.' if you ask him a question.
|
||
|
|
|
||
|
|
He answers 'Whoa, chill out!' if you yell at him.
|
||
|
|
|
||
|
|
He says 'Fine. Be that way!' if you address him without actually saying
|
||
|
|
anything.
|
||
|
|
|
||
|
|
He answers 'Whatever.' to anything else.
|
||
|
|
|
||
|
|
## Instructions
|
||
|
|
|
||
|
|
Run the test file, and fix each of the errors in turn. When you get the
|
||
|
|
first test to pass, go to the first pending or skipped test, and make
|
||
|
|
that pass as well. When all of the tests are passing, feel free to
|
||
|
|
submit.
|
||
|
|
|
||
|
|
Remember that passing code is just the first step. The goal is to work
|
||
|
|
towards a solution that is as readable and expressive as you can make
|
||
|
|
it.
|
||
|
|
|
||
|
|
Please make your solution as general as possible. Good code doesn't just
|
||
|
|
pass the test suite, it works with any input that fits the
|
||
|
|
specification.
|
||
|
|
|
||
|
|
Have fun!
|
||
|
|
|
||
|
|
|
||
|
|
## 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
|
||
|
|
|
||
|
|
Inspired by the 'Deaf Grandma' exercise in Chris Pine's Learn to Program tutorial. [view source](http://pine.fm/LearnToProgram/?Chapter=06)
|