Re: [racket] possibility of defining recontract-all-from-out

2014-09-12 Thread Jon Zeppieri
Yes, this is very helpful. Thank you. -Jon On Fri, Sep 12, 2014 at 10:47 AM, Matthias Felleisen wrote: > > Does this sketch help: > > #lang racket > > ;; define a header file language > (module L racket > ;; specification > (provide export) > ;; ---

Re: [racket] possibility of defining recontract-all-from-out

2014-09-12 Thread Matthias Felleisen
Does this sketch help: #lang racket ;; define a header file language (module L racket ;; specification (provide export) ;; -- ;; implementation (define-syntax (export stx) (syntax-case stx () [(_ file name ctc) #'(define-s

Re: [racket] possibility of defining recontract-all-from-out

2014-09-12 Thread Jon Zeppieri
Matthias, Would you be willing to elaborate on this a bit? Specifically, how is the header specified? Thanks, Jon On Thu, Sep 11, 2014 at 10:35 AM, Matthias Felleisen wrote: > > For a project last year, I developed a suite of syntactic abstractions > that expand into contracted provides. With

Re: [racket] possibility of defining recontract-all-from-out

2014-09-11 Thread Matthias Felleisen
For a project last year, I developed a suite of syntactic abstractions that expand into contracted provides. With the core abstract you specify a header-file-like 'thing' and the exporting module(s) can then require this 'thing' to export identifiers. A re-export would work the same way. If my a

[racket] possibility of defining recontract-all-from-out

2014-09-10 Thread Jon Zeppieri
Rather than listing a large number of identifiers in a (recontract-out ...) spec, I'd like to re-contract everything from a certain required private module. I don't know how to do this. The crux of the problem is that syntax-local-module-required-identifiers can only be called while a provide trans