As usual, thank you very much. Your quick, precise and complete answers are part of what makes using Pollen a joy.
I think adding assignments to current-poly-target in all source files would pollute them. This is redundant information already stated in the file name. That is why I regarded it as a *bad answer*—even though it is a correct one—in my original post. In light of your explainations, what I would *really* like is for (in order of preference): 1. The existence of a current-output-type function, available to *pollen.rkt*. It would return the same things that current-poly-target returns, but would always be in correspondence with the output type in question, regardless of the source file being (for example) .html.pm or *.poly.pm*. 2. When using a source file with an extension other than *.poly.pm*, the current-poly-target parameter is set to the default, which isn’t very helpful. So, in that case, current-poly-target could change to do what I described in the point above. Granted, current-poly-target is not as aptly named to that purpose as current-output-type, but it might fit better with the existing system and documentation. 3. The existence of a metas variable, available to *pollen.rkt*. With it, I could create current-output-type, as you showed in your answer. If you disagree with all these proposals, I guess I’m going to try the idea of using macros to transparently get a hold of metas in *pollen.rkt*, as you described. -- You received this message because you are subscribed to the Google Groups "Pollen" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
