In gerneral, we'd like to run a syntax checker on our ADPs before deployment to ensure no syntax errors made their way through the testing, etc (actaully, this would happen before the testing phase).
Specifically, we had an issue where a '$' was missing from an ADP variable in a rarely used piece of code. That code was used and created an error (and an unhappy customer). It would be nice if we could run our ADPs through a lint-like syntax checker that would verify that things like this don't happen. In this case, it wasn't a missing close-brace or missing quote, so I don't belive info complete would have caught the error. ~John On Thursday 28 August 2003 09:54 am, Dossy wrote: > On 2003.08.28, John M Wright <[EMAIL PROTECTED]> wrote: > > Can anyone recommend an ADP syntax checker? That is, > > some program that will look through a given adp file and > > validate the tcl/adp code. > > You mean you need a static analysis tool for Tcl? More than what "info > complete" does? > > What problem are you trying to solve, exactly? Isn't nsd a decent > syntax checker -- either it runs the code, or it doesn't and throws a > (usually) relevant error message? :-) Of course, this is dynamic > analysis, but ... again, what problem are you trying to solve? > > -- Dossy > > -- > Dossy Shiobara mail: [EMAIL PROTECTED] > Panoptic Computer Network web: http://www.panoptic.com/ > "He realized the fastest way to change is to laugh at your own > folly -- then you can let go and quickly move on." (p. 70) > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the > email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
