Creating a C Documentation Generator - Part 6

Welcome to last post in the series in which we design and implement cdoc

Bump the Version and Add a Release Tag

Fortunately, the only code change needed for the 0.1 release of cdoc is an update to the VERSION macro that we defined in part 1. Currently the VERSION macro is defined as:

#define VERSION "0.0"

With a quick change to:

#define VERSION "0.1"

cdoc now reports that it is version 0.1:

$ make clean cdoc
rm -f cdoc cdoc.o
c99 -O0 -g -c cdoc.c
c99 -o cdoc cdoc.o -O0 -g
$ ./cdoc --version

The source code with this change can be found here. To make things all official we will add a git tag pointing to this commit:

$ git tag v0.1
$ git push origin v0.1

And with that, version 0.1 of cdoc is released.

Future Work

Release 0.1 marks the end of this series, but not the end of cdoc development. The goal of this series was to build a documentation generator from scratch, and after 5+ posts we have done just that1. There is a lot of work that needs to be done to bring cdoc out of an alpha-quality state, and I hope to accomplish that work over the coming months and years. Here is a small sampling of things on the TODO list:

Wrapping Up

Thank you so much for joining me on this journey. I hope you enjoyed reading this series of posts as much as I enjoyed writing them. If you have any questions, comments, or concerns please feel free to reach out to me by email.

Cheers and stay hydrated!


1. Plus each of these posts take a weirdly long time to put together and I have other important stuff I need to do.