Or another hack: put the parameter's value in teh filesystem and use parameter guards to fish it out of there.
This would be useful only if you consider it temporary tho. :) Robby On Wed, Dec 7, 2016 at 2:09 PM, Matthew Flatt <mfl...@cs.utah.edu> wrote: > At Wed, 7 Dec 2016 12:01:24 -0800 (PST), Dan Liebgold wrote: >> On Tuesday, December 6, 2016 at 5:00:47 PM UTC-8, Robby Findler wrote: >> > >> > Perhaps there is another way to achieve the effect you want in a way >> > that is more friendly to creating .zo files? >> > >> >> Yes, this is the crux of the issue. In my case I have a system that deals >> with >> modules that may or may not have .zo files. I'm try to parameterize something >> at compile time for generating the .zo and also at dynamic-require time (when >> the required module may or may not have the corresponding .zo file). >> >> The best solution would be to simplify the compile-time logic such that the >> parameterization isn't required... until then I may have to fix the system >> to >> parameterize the phases separately. > > As a last resort, you might be able to use > `dynamic-require-for-syntax`, which will let you grab a phase-1 value > (such as a parameter) for use in phase-0 code. > > The `dynamic-require-for-syntax` function is a bad idea, but maybe it's > useful in the short run. > > -- > 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. -- 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.
