Wouldn't just running ns_adp_parse on all the ADP files do the trick (with
a catch around it?) If you catch - investigate further..

On Thu, 28 Aug 2003, Dossy wrote:

> On 2003.08.28, John M Wright <[EMAIL PROTECTED]> wrote:
> > 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.
>
> I don't think there's any kind of static or dynamic code analysis tool
> that could tell you that "invoke_wrath_of_god_on foo" should have been
> "invoke_wrath_of_god_on $foo".  Actually, maybe you could -- parse a Tcl
> script into "words" (however you define that) and if any matches a
> variable that has been defined in any scope, display a warning for the
> user running the code inspector to confirm.
>
> After a hundred or two of these heuristic rules, a pretty decent static
> code analyzer could be born.  Neat idea, John.
>
> I wonder if the excellent folks at ActiveState already have (and likely,
> sell) a product like this.
>
> In the meantime, I think better or more rigorous functional testing/QA
> is in order ... unfortunately.
>
> -- 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.

Reply via email to