summaryrefslogtreecommitdiffhomepage
path: root/examples
diff options
context:
space:
mode:
authorTyge Løvset <[email protected]>2020-07-17 12:04:39 +0200
committerTyge Løvset <[email protected]>2020-07-17 12:04:39 +0200
commitb8d9fbae8c4960b30f5114f864e65aa0b4d6c5b5 (patch)
tree7d27bdc629f4541b62b8219a24a9579477ea7287 /examples
parentda4d127cbd65c35fee03411df66eadd34e7a999b (diff)
downloadSTC-modified-b8d9fbae8c4960b30f5114f864e65aa0b4d6c5b5.tar.gz
STC-modified-b8d9fbae8c4960b30f5114f864e65aa0b4d6c5b5.zip
Fixed README's.
Diffstat (limited to 'examples')
-rw-r--r--examples/README.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/examples/README.md b/examples/README.md
index cd6ac4ff..e98ae59d 100644
--- a/examples/README.md
+++ b/examples/README.md
@@ -16,10 +16,10 @@ When your key type consists of several members, you will usually have the hash f
If your key-type stores dynamic memory (e.g. CStr as we will use), it is smart to define a plain-old-data "view" of the your key struct first:
```
#include <stdio.h>
-#include <stc/chash.h>
-#include <stc/cstring.h>
+#include <stc/cmap.h>
+#include <stc/cstr.h>
-// Viking view struct -----------------------
+// Viking view struct
typedef struct VikingVw {
const char* name;
@@ -37,7 +37,7 @@ int vikingvw_equals(const VikingVw* x, const VikingVw* y) {
}
```
-And then the Viking data struct:
+And the Viking data struct:
```
typedef struct Viking {
CStr name;