Regarding overriding globals, a Racket `parameter` is more idiomatic:
https://docs.racket-lang.org/reference/parameters.html
And/or, you could load your config file as a module, like `info.rkt` is.
You might find `dynamic-require` and friends interesting:
https://docs.racket-lang.org/reference/Module_Names_and_Loading.html?q=dynamic-require#%28def._%28%28quote._~23~25kernel%29._dynamic-require%29%29
For one different way to think about config files, especially if your
users are programmers, perhaps your application program could be a
framework, and the config file is the program that the user runs, and
that config file program instantiates the framework:
https://groups.google.com/forum/#!topic/racket-users/6hn9J-r0Nek
--
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.
