Browse Source

Add learning more section

Macoy Madson 2 years ago
  1. 27


@ -630,6 +630,7 @@ There are a number of different things you could do with this:
- Commands could optionally provide a help string
- /Code modification/ could be used to read all functions rather than requiring the use of ~defcommand~
- Support for arguments could be added
* You made it!
If you are feeling overwhelmed, it's okay. Most languages do not expose you to these types of features.
@ -644,3 +645,29 @@ It can take some time to appreciate the power that compile-time code generation
- [[][HotReloadingCodeModifier.cake]] converts module-local and global variables into heap-allocated variables automatically, which is an essential step to making hot-reloadable code possible
You can see that this one feature makes possible many things which would be very cumbersome to do without it.
* Learning more
** Reading documentation
The ~doc/~ folder contains many files of interest, especially [[][]]. There you will find much more detailed documentation than this tutorial provides.
** Cakelisp self-documentation
Cakelisp provides some features to inspect its built-in generators. From the command line:
./bin/cakelisp --list-built-ins
...lists all the possible generators built in to Cakelisp. This is especially useful when you forget the exact name of a built-in.
./bin/cakelisp --list-built-ins-details
This version will list all built-ins as well as provide details for them.
** Reading code
The best way to learn Cakelisp is to read existing code.
There are examples in ~test/~ and ~runtime/~. You can find extensive real-world usage of Cakelisp on [[][]].
[[][GameLib]] is the closest thing to a package manager you will find in Cakelisp land. It provides powerful features as well as easy importing for a number of 3rd-party C and C++ libraries.