[racket] How can I dump (display) the variables defined in current the global environment

From: Matthias Felleisen (matthias at ccs.neu.edu)
Date: Mon Mar 2 11:56:56 EST 2015

This is about the best advice you can get. 

I want to add that neither Racket nor the teaching languages for How to Design Programs correspond exactly to the (minimal) language of TLS. These languages are close but they differ from the language of TLS in (1) the names of the functions and (2) occasionally the assumed behavior, especially error behavior. If you are a beginner, consider using the Beginning Student Language with List Abbreviations for chapters 1 thru 7 and Intermediate plus Lambda for the remaining chapters. 

You can find these languages after launching DrRacket via the -> Language -> Choose Languages menu. 

-- Matthias

On Mar 1, 2015, at 7:54 PM, Jordan Johnson wrote:

> On Mar 1, 2015, at 5:37 PM, Rufus <rlaggren at mail.com> wrote:
>> And also
>> a function to save this state (variables in the global environment) in a
>> fashion that could be quickly/easily (ie one short function call) be
>> reloaded the next day to continue from where I left off.
> The typical workflow in DrRacket is to use the Definitions pane for this.
> If I were working through TLS from scratch in DrRacket, here is how I would do it, knowing what I now know:
> Start a new file when I start a new chapter.
> When a definition comes up, add it to the Definitions pane, then save and click “Run”.
> When a name from a previous chapter is referenced in an expression or definition, copy it in from that chapter’s file, then save and click “Run”.
> When expressions are being evaluated, type the expressions in the Interactions pane.
> I don’t remember if there is use of set! in TLS — that would complicate things a bit — but I don’t think there was much if any.
> HTH,
> jmj
> ____________________
>  Racket Users list:
>  http://lists.racket-lang.org/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20150302/41d4ac26/attachment.html>

Posted on the users mailing list.