exercism

Exercism solutions.
git clone git://code.dwrz.net/exercism
Log | Files | Refs

README.md (1437B)

      1 # Word Count
      2 
      3 Given a phrase, count the occurrences of each word in that phrase.
      4 
      5 For example for the input `"olly olly in come free"`
      6 
      7 ```text
      8 olly: 2
      9 in: 1
     10 come: 1
     11 free: 1
     12 ```
     13 
     14 ## Getting Started
     15 
     16 Make sure you have read the "Guides" section of the
     17 [C track](https://exercism.io/my/tracks/c) on the Exercism site. This covers
     18 the basic information on setting up the development environment expected
     19 by the exercises.
     20 
     21 
     22 ## Passing the Tests
     23 
     24 Get the first test compiling, linking and passing by following the [three
     25 rules of test-driven development][3-tdd-rules].
     26 
     27 The included makefile can be used to create and run the tests using the `test`
     28 task.
     29 
     30     make test
     31 
     32 Create just the functions you need to satisfy any compiler errors and get the
     33 test to fail. Then write just enough code to get the test to pass. Once you've
     34 done that, move onto the next test.
     35 
     36 [3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
     37 
     38 As you progress through the tests, take the time to refactor your
     39 implementation for readability and expressiveness and then go on to the next
     40 test.
     41 
     42 Try to use standard C99 facilities in preference to writing your own
     43 low-level algorithms or facilities by hand.
     44 
     45 ## Source
     46 
     47 This is a classic toy problem, but we were reminded of it by seeing it in the Go Tour.
     48 
     49 ## Submitting Incomplete Solutions
     50 It's possible to submit an incomplete solution so you can see how others have completed the exercise.