MSasu Posted January 7, 2010 Posted January 7, 2010 One strong point of AutoLISP language is the ability to construct, set and list variables at run-time using READ and EVAL statements; therefore this result in a great design flexibility not available in other languages. But using the EVAL statement into code will raise a warning message when the source is compiled into VLX file: (setq theValue 1) (eval (read "theValue")) [color=blue]warning: run time evaluated expression: (READ "theValue")[/color] For sure, the compilation is completed, but I’m still wandering why they considered that there is an issue and how (and if) this may affect in some circumstances the usage of that routine? Quote
Lee Mac Posted January 7, 2010 Posted January 7, 2010 I too have seen these warnings - I wonder whether it is just to warn of possible malicious code? Quote
MSasu Posted January 7, 2010 Author Posted January 7, 2010 This may be true – unfortunately wasn’t able to find up to now an "official" explanation. So, each compilation of some of my routines is wrapped in some stress… Quote
Lee Mac Posted January 7, 2010 Posted January 7, 2010 This may be true – unfortunately wasn’t able to find up to now an "official" explanation. So, each compilation of some of my routines is wrapped in some stress… Perhaps try here? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.