53 lines
2.1 KiB
Markdown
53 lines
2.1 KiB
Markdown
# Meetup
|
|
|
|
Calculate the date of meetups.
|
|
|
|
Typically meetups happen on the same day of the week.
|
|
|
|
Examples are
|
|
|
|
- the first Monday
|
|
- the third Tuesday
|
|
- the Wednesteenth
|
|
- the last Thursday
|
|
|
|
Note that "Monteenth", "Tuesteenth", etc are all made up words. There
|
|
was a meetup whose members realised that there are exactly 7 days 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.
|
|
|
|
## 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
|
|
|
|
Jeremy Hinegardner mentioned a Boulder meetup that happens on the Wednesteenth of every month [view source](https://twitter.com/copiousfreetime)
|