queen-attack: initial commit
This commit is contained in:
parent
0f23771e94
commit
92b98cf850
4 changed files with 310 additions and 0 deletions
61
cpp/queen-attack/README.md
Normal file
61
cpp/queen-attack/README.md
Normal file
|
|
@ -0,0 +1,61 @@
|
|||
# Queen Attack
|
||||
|
||||
Write a program that positions two queens on a chess board and indicates whether or not they are positioned so that they can attack each other.
|
||||
|
||||
In the game of chess, a queen can attack pieces which are on the same
|
||||
row, column, or diagonal.
|
||||
|
||||
A chessboard can be represented by an 8 by 8 array.
|
||||
|
||||
So if you're told the white queen is at (2, 3) and the black queen at
|
||||
(5, 6), then you'd know you've got a set-up like so:
|
||||
|
||||
```plain
|
||||
_ _ _ _ _ _ _ _
|
||||
_ _ _ _ _ _ _ _
|
||||
_ _ _ W _ _ _ _
|
||||
_ _ _ _ _ _ _ _
|
||||
_ _ _ _ _ _ _ _
|
||||
_ _ _ _ _ _ B _
|
||||
_ _ _ _ _ _ _ _
|
||||
_ _ _ _ _ _ _ _
|
||||
```
|
||||
|
||||
You'd also be able to answer whether the queens can attack each other.
|
||||
In this case, that answer would be yes, they can, because both pieces
|
||||
share a diagonal.
|
||||
|
||||
## 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).
|
||||
|
||||
## Source
|
||||
|
||||
J Dalbey's Programming Practice problems [http://users.csc.calpoly.edu/~jdalbey/103/Projects/ProgrammingPractice.html](http://users.csc.calpoly.edu/~jdalbey/103/Projects/ProgrammingPractice.html)
|
||||
Loading…
Add table
Add a link
Reference in a new issue