Re: TOAD Editor - Strange behavior

Small changes from the last list of rule changes...


The following rules have been added, merged, or improved.

Rule 4811 has been combined with 4809.

We have added these rules:

2105, 2106, 2110-2114, 2116, 2118, 2120, 2122, 2124 – 2129, 2133, 5405, 5901, 5902, 5904 – 5907, 5910, 5914, 5917, 6601 – 6610, 6811.

These rules use a new XPath engine:

2401, 4402, 4404, 4405, 4406, 4802, 5810, 6414.

These rules use improved XPath queries:

2610, 2827, 3001, 3003, 3017, 4201, 4213, 4603, 4809, 4812, 5805, 5813, 5825, 5826, 6202, 6413.


On Mar 14, 2012, at 11:52 AM, Bert Scalzo wrote:



There are lots of “dead code” scenarios we’d like to identify – but that requires an expression parser and then having semnatic knowledge – whereas most of code analysis at this stage is still syntactical in nature. But it’s a constant point of roadmap discussion :)

From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Simoneau, Roger
Sent: Wednesday, March 14, 2012 10:44 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [toad] TOAD Editor - Strange behavior


>> Probably 4213 – Use CASE statement rather than a complex conditional IF statement.

If you run a code check against it, I’d expect it to identify the first two paths in the IF statement as logical paths that will never occur too……

But I suppose that depends how smart the code check is :)

Roger S.

________________________________
This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply.