From 9aabfe8f0ea23804556340629368dc61bc14f16c Mon Sep 17 00:00:00 2001 From: Matthew Butterick Date: Wed, 24 Apr 2019 19:28:19 -0700 Subject: [PATCH] clarity --- quad/quad/scribblings/quad.scrbl | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/quad/quad/scribblings/quad.scrbl b/quad/quad/scribblings/quad.scrbl index ac33b522..62cd1681 100644 --- a/quad/quad/scribblings/quad.scrbl +++ b/quad/quad/scribblings/quad.scrbl @@ -1,6 +1,6 @@ #lang scribble/manual -@(require scribble/eval (for-label (except-in pollen #%module-begin) xml racket/base racket/draw) +@(require scribble/eval (for-label (except-in pollen txexpr #%module-begin) xml racket/base racket/draw) pollen/scribblings/mb-tools) @(define my-eval (make-base-eval)) @@ -492,6 +492,8 @@ If you're a writer, you might prefer to use the high-level representation (like If you're a developer, you might prefer to use the lower-level representation for precision. For instance, a @racketmodname[pollen] author who wanted to generate a PDF could design tag functions that emit Q-expressions, and then pass the result to Quadwriter for conversion to PDF. +@margin-note{Because Q-expressions are a subset of X-expressions, you can apply any tools that work with X-expressions (for instance, the @racketmodname{txexpr} library).} + Or, you can aim somewhere in between. Like everything else in Racket, you can design functions & macros to emit the pieces of a Q-expression using whatever interface you prefer. @subsection{I don't like Quadwriter}