On Wed, Nov 21, 2012 at 8:58 PM, Nadeem Abdul Hamid <nad...@acm.org> wrote: >> Maybe this would help, I have only used Check Syntax two or three >> times ever when I wanted to rename a variable because it was used in >> more than 5 places. What other problems does it solve? >> > > It catches syntax errors (name typos, etc.) earlier. It allows jumping (via > the arrows) to binding (definition) and bound (usage) sites of identifiers. > It helps you recall or find out which 'require'd module a given identifier > is imported from. And it helps show the 'the thing in the upper right hand > corner', which is convenient when you need to quickly refresh your memory on > the number/order of parameters of a function, without having to switch to a > web browser. And if that thing isn't helpful, the popup context menu allows > you to jump directly to the full documentation for a given definition. The > first item listed (i.e. early discovery of syntax errors) is sufficient > benefit in itself, as far as my experience goes. (And I believe that is one > of the primary benefits and uses in the other IDEs I mentioned, especially > since many of those are designed for statically typed languages so the class > of errors that can be caught at compilation is larger than (untyped) > Racket.)
Thanks! At my day job I've relied on that for systems with three-thousand plus classes where the complexity was too much for any one person to take in. ____________________ Racket Users list: http://lists.racket-lang.org/users
