Neat. 

Keep in mind that the API of a module should be considered a specification 
(purpose, signature) that the module body (generated later) lives up to. No, 
this is not how we always work in practice because software evolves, but that 
is the principle. 




> On May 8, 2018, at 11:21 AM, Dexter Lagan <dexterla...@gmail.com> wrote:
> 
> Hi folks,
> 
>   I developed a provide form generator to take the pain out of writing module 
> headers: 
> 
> https://github.com/dexterlagan/provide-generator
> 
>  It works great, but I wonder if there wouldn’t be a simpler and more 
> standard way to write this. My original idea was to parse the module syntax 
> and simply delete the body of each define form, converting each function 
> definition to string and use it as comment to each provide element. I 
> couldn’t make it work that way, so I had to switch from syntax objects to 
> strings half-way and handle it by hand. Any insight?
> 
> Thanks!
> 
> Dex
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to