Huh, I must have missed this the first time around. I've run into this sort
of thing multiple times before and it usually brings me to this question:
What if the configuration file was the main module of your app, instead of
something imported by your app?
Think about it. The "my-project/config
For the benefit of posterity, while I haven't actually solved the
cycle-in-loading error, I was able to get the results that I wanted in this
case by:
1. Implementing the language as a `module` (not `module*` or `module+`)
submodule of "my-project/config.rkt", including a
(module reader s
I have often done it that way, too. In this case I decided to use a #lang
for a few reasons:
- The values for some of the parameters are not readable.
- In some cases I want to do a little bit of work to calculate the
value. For instance, "production.rkt" reads in the values of some API k
Hi Philip,
I don't have an answer to your problem, but I'm curious as to what do you store
in "local.rkt" and "production.rkt" to justify such a complicated solution.
In the projects that I worked on (Racket or otherwise), local vs production
differ in the values for different parameters, which
4 matches
Mail list logo
