Very nice tool for checking that a form has no other external dependencies than intended. Two remarks though:
1: Because all references to imported bindings (both variables and syntactic forms) have arrows too, there is an abundance of non informative arrows (for example to the #lang scheme line) that obscure the arrows I am interested in, id est those that point between bindings and references within the current module only. Id est, the arrows to require forms can be omitted as far as I am concerend. 2: How do I untack? Thanks Jos. ----- Original Message ----- From: "Ryan Culpepper" <[email protected]> To: <plt-dev at list.cs.brown.edu> Sent: Monday, February 09, 2009 6:24 AM Subject: [plt-dev] arrows crossing selection > I've just snuck a new feature into Check Syntax. You can now tack all > binding arrows that cross the editor's selection boundary. That is, they > have one end inside the selection and one end outside. One use is to find > free variables in an expression you want to lift out as a separate > procedure. > > To use it: Run Check Syntax, highlight a region of code, and right-click > to get the Check Syntax context menu. It has an additional item labeled > "Tack arrows crossing selection". > > If people like it, I can tidy it up and add variants (eg, untack, don't > include arrows for module imports). If people don't like it, I can take it > out again. Feedback welcome. > > Ryan > > _________________________________________________ > For list-related administrative tasks: > http://list.cs.brown.edu/mailman/listinfo/plt-dev
