Good choice :-) ;; ---
I think Robby translated the recommendations of the style guide just right. BTW, I didn't think it mentions named let only let. Indeed, I can't find a recommendation of preferring defined over named let. ;; --- A comment on your commenting style. I tried to read your code and Robby's version of it, and I found that the large number of comments distracted me and weren't helpful at all. I'd recommend using variable and function names instead that convey the same idea as the comments. Try it out. -- Matthias On Jun 29, 2014, at 9:09 AM, Jos Koot wrote: > Thanks. > I always use DrRacket for editing racket code. > Jos. > >> -----Original Message----- >> From: Greg Hendershott [mailto:greghendersh...@gmail.com] >> Sent: domingo, 29 de junio de 2014 5:55 >> To: Jos Koot >> Cc: dev; jja.k...@gmail.com >> Subject: Re: [racket-dev] 2htdp/image Feature Suggestion >> >> On Mon, Jun 23, 2014 at 9:44 PM, Jos Koot <jos.k...@gmail.com> wrote: >>> style. Writing this, the idea comes up in my mind that it >> should be possible >>> to do some transformations to the recommended style by >> means of redex. Or >>> may be by means of syntax-case while limiting the >> transformers to the >>> desired level of expansion. Both instuments are interesting >> enough for me to >>> give it a try. If I am able to do something usefull in this >> sense, you'll >>> hear of me, but give me some time, please. >> >> If you use Emacs, check out Ryan's sexp-rewrite mode. IIUC he's >> implemented `syntax-parse`-like functionality in Elisp: >> >> https://github.com/rmculpepper/sexp-rewrite >> >> >> p.s. In a similar spirit, but for Clojure, and IIUC implemented >> leveraging paredit: >> >> https://github.com/clojure-emacs/clj-refactor.el > > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev _________________________ Racket Developers list: http://lists.racket-lang.org/dev
