I agree that those sound goals sound like a poor fit for `module+`.
It's possible that `racket/package` provides something closer to the
namespace-management tools that you need.
Generally, I think you'll find more success by manipulating bindings
and lexical context (in the sense of
(Sorry for the long delay!)
I think that defining a paragraph style for Latex is the right answer
to avoid indentation. In case you haven't yet done that, here's a hack:
use `(elem #:style noindent)` as the first element of of the
paragraph. That works because it generates `\noindent` in the
I wonder if base64-encode should rather be patched with a #:last-newline?
(Default #t) argument.
Tim
On 7 May 2015 17:37:18 BST, Tim Brown tim.br...@cityc.co.uk wrote:
Folks,
I've just tried to use web-server/http-digest-auth, and
it seems that make-digest-auth-header generates an invalid
The problem that you're hitting is that the `#%module-begin` form of
`racket` forces partial expansion of the module body to detect
definitions before it proceeds to expand expressions. That's why
`define-values` complains about a full expansion in context; it's not
supposed to be fully expanded,
I have no problem with these names --- the `scribble` exports are
unlikely to ever collide, since we rarely resort to capital letters ---
but I can't help thinking that the language of the metadata should
specified explicitly.
Concretely, instead of
#lang racket/base
maybe the file should
That sounds good. Although I haven't used it in awhile, I recall needing to
slice that off more often than keeping it.
On May 7, 2015 2:22 PM, Tim Brown t...@timb.net wrote:
I wonder if base64-encode should rather be patched with a #:last-newline?
(Default #t) argument.
Tim
On 7 May 2015
On May 6, 2015, at 7:16 PM, Matthew Butterick m...@mbtype.com wrote:
A few notes about what I learned when converting my `sugar` library to a dual
Typed Racket / Racket library (in part because of performance considerations).
Folks,
I've just tried to use web-server/http-digest-auth, and
it seems that make-digest-auth-header generates an invalid header
(or at least one that upsets Firefox).
The definition of make-digest-auth-header(*) uses base64-encode
to generate the nonce. base64-encode is documented as:
the
8 matches
Mail list logo
