SEE ATTACHMENT
Turn off options -> code analysis -> check for violations as you type.
Or you could look at the violation and fix it.
Or you could create style set without that rule and set it to the default rule set.
On Mar 14, 2012, at 6:50 AM, "Aci Polajnar" wrote:
Hi
Editing ORACLE objects with TOAD Editor, I get strange picture with lines:
How can I gen a normal picture, without lines ??
Thank you and best regards!
... Create a rule set...
Not style set
Stupid auto correct!
On Mar 14, 2012, at 6:54 AM, "Gregory Liss" wrote:
Turn off options -> code analysis -> check for violations as you type.
Or you could look at the violation and fix it.
Or you could create style set without that rule and set it to the default rule set.
On Mar 14, 2012, at 6:50 AM, "Aci Polajnar" wrote:
Hi
Editing ORACLE objects with TOAD Editor, I get strange picture with lines:
How can I gen a normal picture, without lines ??
Thank you and best regards!
... Create a rule set...
Not style set
Stupid auto correct!
On Mar 14, 2012, at 6:54 AM, "Gregory Liss" wrote:
Turn off options -> code analysis -> check for violations as you type.
Or you could look at the violation and fix it.
Or you could create style set without that rule and set it to the default rule set.
On Mar 14, 2012, at 6:50 AM, "Aci Polajnar" wrote:
Hi
Editing ORACLE objects with TOAD Editor, I get strange picture with lines:
How can I gen a normal picture, without lines ??
Thank you and best regards!
Curios – what rule was he violating because the code looks OK to me ???
Probably 4213 – Use CASE statement rather than a complex conditional IF
statement.
Also, for 11.5, we’re no longer putting the blue squiggles over the entire IF
statement, just the IF itself.
Much nicer – thanks for the extra info – very helpful J
Much nicer – thanks for the extra info – very helpful J
This will be in the “What’s new” as well but we’ve made a few changes to the
rules:
2101 - 2116 - added
2118 - added
2119 - added
2120 - added
2122 - added
2123 - 2129 - added
2131 - added
2132 - added
2133 - added
2401 - changed - uses new XPath engine
2610 - changed - improved XPath query
2827 - changed - improved XPath query
2832 - added
3001 - changed - improved XPath query
3003 - changed - improved XPath query
3017 - changed - improved XPath query
4201 - changed - improved XPath query
4213 - changed - improved XPath query
4402 - changed - uses new XPath engine
4404 - changed - uses new XPath engine
4405 - changed - uses new XPath engine
4406 - changed - uses new XPath engine
4603 - changed - improved XPath query
4802 - changed - uses new XPath engine
4809 - changed - improved XPath query
4811 - combined with 4809
4812 - changed - improved XPath query
5405 - added
5805 - changed - improved XPath query
5810 - changed - uses new XPath engine
5813 - changed - improved XPath query
5825 - changed - improved XPath query
5826 - changed - improved XPath query
5901 - 5922 - added
6202 - changed - improved XPath query
6413 - changed - uses new XPath engine
6414 - changed - uses new XPath engine
6601 - 6610 - added
6811 - added
Thank you, Gregory
Best regards!
On 14.3.2012 11:54, Gregory Liss wrote:
Turn off options -> code analysis -> check for violations as you type.
Or you could look at the violation and fix it.
Or you could create style set without that rule and set it to the default
rule set.
On Mar 14, 2012, at 6:50 AM, "Aci Polajnar" wrote:
> Hi
>
> Editing ORACLE objects with TOAD Editor, I get strange picture with lines:
>
>
>
> How can I gen a normal picture, without lines ??
>
> Thank you and best regards!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.
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 J
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 J