Whoops that first example was missing a lozenge, should’ve been like so:

> #lang pollen
> ◊(require certain/module)
> ···



> On Jul 26, 2019, at 7:57 PM, Matthew Butterick <m...@mbtype.com> wrote:
> 
> 
>> On 07 26 19, at 3:03 PM, Jen Hutton <jenhut...@gmail.com> wrote:
>> 
>> Thanks. That fixed it, as well as adding (provide (all-defined-out)) to 
>> pollen.rkt. I seemed to have left that out too.
> 
> 
> 
> BTW though you can `require` any module within a Pollen source file, for 
> instance:
> 
> #lang pollen
> (require certain/module)
> ···
> 
> You can also propagate it via "pollen.rkt" with `all-from-out`, for instance:
> 
> #lang racket
> (require certain/module)
> (provide (all-from-out certain/module))
> ···
> 
> 
> This has the same effect, because anything exported from "pollen.rkt" is 
> implicitly available in a Pollen source file that relies on it.
> 
> 
> -- 
> 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 pollenpub+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pollenpub/2E381043-C583-4305-A59D-E097E6138DA3%40mbtype.com.

-- 
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 pollenpub+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pollenpub/8F3F6C14-7E84-4B55-B1E8-14D3FA24AA5C%40mbtype.com.

Reply via email to