Thanks Matthew. That worked, but I don't fully understand why. Is having
2 reader langs before the 3rd module lang unique to s-exp here, or is it
possible to chain multiple custom reader languages together like you've
done?
I assumed that #lang at-exp "my-lang.rkt" should work, since I'm wanting
Ok thanks. So it's not as simple as knowing the phase level that
corresponds to documentation time and then providing with for-meta? I was
trying something along those lines but likely am misguided.
On Sat, Jan 11, 2014 at 6:45 PM, Matthew Flatt wrote:
> There's no `(provide (for-doc ...))`,
Beta version is ready.
No docs yet. Simply look into main.rkt -- there are examples of usage and
drop-in replacements for pure-port.
TODO: IDNA for canonical names (RFC 5890) and support for
http://publicsuffix.org/list/
Question to all: how to provide extensibility for module?
One may wan
3 matches
Mail list logo
