Topic: Is there a way to collect all variables from the code?

[HasanCAD]

Should we collect variables from the code manually or there is better way?

[irneb]

Well if you mean you want to figure out which variables your code leaves as globals, then try this tut from Lee Mac: http://www.lee-mac.com/quicklocalising.html

If you want to figure out all the variables from the code (local or not), then you could remove the local declarations from all the defuns first and then go through that VLIDE check. Just remember to re-localize them, else you could get lots of errors.

[Marc'Antonio Alessi]

Should we collect variables from the code manually or there is better way?

I use this from: R. Robert Bell, MCSE
(defun C:Leak (/ lVars orgAtoms) ...

http://www.thecadforums.com/autocad-customization/26072-nullifying-declared-variables-automatically-2.html

http://forums.autodesk.com/t5/Visual-LISP-AutoLISP-and-General/QUESTION/td-p/807073

http://forums.autodesk.com/t5/Visual-LISP-AutoLISP-and-General/Nullifying-the-declared-variables-automatically/td-p/1000192/page/3

[HasanCAD]

Well if you mean you want to figure out which variables your code leaves as globals, then try this tut from Lee Mac: http://www.lee-mac.com/quicklocalising.html

If you want to figure out all the variables from the code (local or not), then you could remove the local declarations from all the defuns first and then go through that VLIDE check. Just remember to re-localize them, else you could get lots of errors.

Thanx irneb

[irneb]

I use this from: R. Robert Bell, MCSE
(defun C:Leak (/ lVars orgAtoms) ...

Just be careful of using such all the time. You could easily be clearing some global variable of some totally different piece of code (which you don't know about or forgot about or it's coming in from something else) that should have been left as is. Another issue using this "Clear Globals to NIL" idea is if you reuse that function inside another, it's quite possible to have naming conflicts which would then clear the calling function's local vars instead of the called function's global vars. Not saying you should not use this, but just be wary of errors which could come about because of it.

My advise is to list which variables are (still) global from your function then modify your function to localize them. It's the least problematic in the long run - especially with a Dynamic Scoped language like AutoLisp.

[Marc'Antonio Alessi]

I use this from: R. Robert Bell, MCSE
(defun C:Leak (/ lVars orgAtoms) ...

Just be careful of using such all the time. You could easily be clearing some global variable of some totally different piece of code (which you don't know about or forgot about or it's coming in from something else) that should have been left as is. Another issue using this "Clear Globals to NIL" idea is if you reuse that function inside another, it's quite possible to have naming conflicts which would then clear the calling function's local vars instead of the called function's global vars. Not saying you should not use this, but just be wary of errors which could come about because of it.

My advise is to list which variables are (still) global from your function then modify your function to localize them. It's the least problematic in the long run - especially with a Dynamic Scoped language like AutoLisp.

Thanks for answer, I use "C:Leak" only for rough work, while I do the final check with VLIDE during compilation .

Marco

[qjchen]

I often use lisplink to write the lsp code.
It has such function



but it also has some bug, like it will take "pi" or "1e3" as local variable, so it should be noticed.

[irneb]

Thanks nice one, is it possible to modify LispLink's list of global / default symbols? Perhaps then it might function properly in all cases. Or someone could go and write a Python addon for Notepad++ to do the same there 

[qjchen]

Thanks nice one, is it possible to modify LispLink's list of global / default symbols? Perhaps then it might function properly in all cases. Or someone could go and write a Python addon for Notepad++ to do the same there 

Hi, irneb, do you mean the syntax.dat in the installed directory?

[irneb]

Hi, irneb, do you mean the syntax.dat in the installed directory?

Don't know, perhaps that might help. I've never used LispLink, but I imagine such things must be customizable.