Re: Using parameters for customization
Peter McGoron 02 Jul 2026 21:39 UTC
On 5/15/26 09:31, Sergei Egorov wrote:
> I probably need to clarify it: only one of the libraries exporting 'pp'
> should be imported, they are not supposed to complement each other in
> the same program.
I think this is an issue for using this SRFI in libraries. One would
have to keep consistent which pretty-print library recursively across
all imported libraries.
I think a single parameter object that contains the complete
customization state is better and easier to reason about.
_______________
As an aside, I think the variable-argument `pp` and `pp*` should be
moved up to the `basic` library, since that library has parameters that
can be passed to them as keywords. Also, `pp*` should take an
association list instead of the apply-list as its final argument.
Currently the procedure is equivalent to `apply`. A user is more likely
to store a map from keywords to objects in an association list.
-- Peter McGoron