summary refs log tree commit diff stats
path: root/c/leap/README.md
diff options
context:
space:
mode:
authorAndinus <andinus@nand.sh>2021-08-27 09:47:13 +0530
committerAndinus <andinus@nand.sh>2021-08-27 09:47:13 +0530
commit4607171bb302ba81229ed5686d7c6f546d27a33d (patch)
treea511fed23a62fca764f2bcce3a28747441aaef09 /c/leap/README.md
parent346da9a7e08af19141a791978b3650bb150eafb0 (diff)
downloadexercism-4607171bb302ba81229ed5686d7c6f546d27a33d.tar.gz
C: Solve leap exercise
Diffstat (limited to 'c/leap/README.md')
-rw-r--r--c/leap/README.md62
1 files changed, 62 insertions, 0 deletions
diff --git a/c/leap/README.md b/c/leap/README.md
new file mode 100644
index 0000000..e9f5e7b
--- /dev/null
+++ b/c/leap/README.md
@@ -0,0 +1,62 @@
+# Leap
+
+Given a year, report if it is a leap year.
+
+The tricky thing here is that a leap year in the Gregorian calendar occurs:
+
+```text
+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.
+
+## Notes
+
+Though our exercise adopts some very simple rules, there is more to
+learn!
+
+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 "Guides" section of the
+[C track][c-track] on the Exercism site. 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][3-tdd-rules].
+
+The included makefile can be used to create and run the tests using the `test`
+task.
+
+    make test
+
+Create just the functions you need 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, move onto the next test.
+
+As you progress through the tests, take the time to refactor your
+implementation for readability and expressiveness and then go on to the next
+test.
+
+Try to use standard C99 facilities in preference to writing your own
+low-level algorithms or facilities by hand.
+
+## Source
+
+JavaRanch Cattle Drive, exercise 3 [http://www.javaranch.com/leap.jsp](http://www.javaranch.com/leap.jsp)
+
+## Submitting Incomplete Solutions
+It's possible to submit an incomplete solution so you can see how others have completed the exercise.
+
+[c-track]: https://exercism.io/my/tracks/c
+[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd