[racket] tool: show module exports

That's damn cute! 



On Jul 21, 2010, at 9:41 PM, Stevie Strickland wrote:

> On Jul 21, 2010, at 9:33 PM, Jon Rafkind wrote:
>> On 07/21/2010 05:26 AM, Robby Findler wrote:
>>> One, non-optimal way to get the contracts is to evaluate the module
>>> and use object-contract on the exports (non-optimal because dependent
>>> contracts will have ...s in them, etc).
>> `object-contract' looks like its only for stuff from the class system, right? Did you mean some other function?
> 
> I believe he meant 'value-contract'.  That'll give you the contract for values that have it stored appropriately, and then you can use 'contract-name' on the contract to get a s-expression representation.
> 
> Stevie