I generally second the idea of doing a configuration file format like
"info.rkt" (but not using that particular filename, unless your program
is tools for Racket development projects).
An advantage of this format is that you then have a few different
options for how to use the file. Specifically, if the file format looks
like Racket code, you can use it via `read`/`read-syntax` (while setting
parameters for safety), via `dynamic-require`, or via `require`.
And you can change your mind how to use the format later, without
requiring end users to change the documented file format they use.
If you eventually go to `dynamic-require` or `require`, then you can add
more Racket language features to the "configuration file", and then it's
an extensibility language, or your program is a domain-specific
framework. This is also a good way to ease people into extension, and
into using Racket.
Neil V.
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
