60 lines
2.3 KiB
Markdown
60 lines
2.3 KiB
Markdown
# Leap
|
|
|
|
Write a program that will take a year and report if it is a leap year.
|
|
|
|
The tricky thing here is that a leap year in the Gregorian calendar occurs:
|
|
|
|
```plain
|
|
on every year that is evenly divisible by 4
|
|
except every year that is evenly divisible by 100
|
|
unless the year is also evenly divisible by 400
|
|
```
|
|
|
|
For example, 1997 is not a leap year, but 1996 is. 1900 is not a leap
|
|
year, but 2000 is.
|
|
|
|
If your language provides a method in the standard library that does
|
|
this look-up, pretend it doesn't exist and implement it yourself.
|
|
|
|
## Notes
|
|
|
|
For a delightful, four minute explanation of the whole leap year
|
|
phenomenon, go watch [this youtube video][video].
|
|
|
|
[video]: http://www.youtube.com/watch?v=xX96xng7sAE
|
|
|
|
## 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
|
|
|
|
JavaRanch Cattle Drive, exercise 3 [view source](http://www.javaranch.com/leap.jsp)
|