[racket] What are some good practices of reading racket source code

On Sat, Feb 2, 2013 at 1:04 PM, Grant Rettke <grettke at acm.org> wrote:
> In that same vein, what are good entry points for learning about how
> racket works? I think, learning how the #lang line itself works might
> be one of them?

The Guide has an introduction to how #lang works:

    http://docs.racket-lang.org/guide/languages.html

That may be a good place to start.


If you're looking for example-driven approaches, perhaps:

    http://hashcollision.org/brainfudge/

may be applicable?  I also wrote up a quick-and-dirty example of
writing a #lang for a simple DSL for ascii diagrams for 'ragg':

    http://hashcollision.org/ragg/#(part._.Example__a_small_.D.S.L_for_.A.S.C.I.I_diagrams)



For a more substantial example, perhaps Jens's minipascal project?

    https://pkg.racket-lang.org/info/minipascal