On Fri, Sep 9, 2011 at 11:23 AM, Grant Rettke <gret...@acm.org> wrote: > Hi, > > At work I've inherited a financial application whose model that is too > complicated to be documented. > > It has got me really curious how I might use Racket to document, > understand, and implement the model so that we can really flesh out > how it works. It would be useful purely from that regard, and also if > we ever migrated to a different technology (than Java). > > What approaches, techniques, or features of Racket do you think might > be interesting?
Contracts! Also, domain-specific languages implemented via macros. > My list: Typed Racket, in-code documentation, Rackunit, > purely-functional or perhaps classes and interfaces, not sure what > would be easier for people to read. > > Best wishes, > > Grant > > -- > http://www.wisdomandwonder.com/ > ACM, AMA, COG, IEEE > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/users > -- sam th sa...@ccs.neu.edu _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
