66 lines
2.4 KiB
Markdown
66 lines
2.4 KiB
Markdown
# Meetup
|
|
|
|
Calculate the date of meetups.
|
|
|
|
Typically meetups happen on the same day of the week. In this exercise, you
|
|
will take a description of a meetup date, and return the actual meetup date.
|
|
|
|
Examples of general descriptions are:
|
|
|
|
- The first Monday of January 2017
|
|
- The third Tuesday of January 2017
|
|
- The wednesteenth of January 2017
|
|
- The last Thursday of January 2017
|
|
|
|
The descriptors you are expected to parse are:
|
|
first, second, third, fourth, fifth, last, monteenth, tuesteenth, wednesteenth,
|
|
thursteenth, friteenth, saturteenth, sunteenth
|
|
|
|
Note that "monteenth", "tuesteenth", etc are all made up words. There was a
|
|
meetup whose members realized that there are exactly 7 numbered days in a month
|
|
that end in '-teenth'. Therefore, one is guaranteed that each day of the week
|
|
(Monday, Tuesday, ...) will have exactly one date that is named with '-teenth'
|
|
in every month.
|
|
|
|
Given examples of a meetup dates, each containing a month, day, year, and
|
|
descriptor calculate the date of the actual meetup. For example, if given
|
|
"The first Monday of January 2017", the correct meetup date is 2017/1/2.
|
|
|
|
## 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
|
|
|
|
Jeremy Hinegardner mentioned a Boulder meetup that happens on the Wednesteenth of every month [https://twitter.com/copiousfreetime](https://twitter.com/copiousfreetime)
|
|
|
|
## 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
|