| Author |
 Topic  |
|
|
Toni Schilling
New Member
Germany
3 Posts |
 Posted - Mar 03 2010 : 09:20:13 AM
|
Hello folks!
Is this a bug or a feature?
Writing the following in my source ...
/*
* The class decclares template < int N > void foo().
* The class decclares template < int N> void foo().
* The class decclares template < int N > void foo().
*/
/*
* The class decclares template < int N > void foo().
* The class decclares template< int N > void foo().
* The class decclares template < int N > void foo().
*/
... VA shows spelling errors only in the 1st and 2nd line of the comment but _not_ in the 3rd.
Spell check seems to be off for the remaining comment when '>' or '<' appears directly after a word ("template<" or "N>").
Does anybody know ...?
Toni Schilling
(I'm using VA 10.5.1722.0 and VS2008) |
|
|
feline
Whole Tomato Software
United Kingdom
18947 Posts |
Posted - Mar 04 2010 : 10:15:44 AM
|
I am seeing the same effect here. Thank you for the clear description.
case=29867
Sometimes XML tags in comments can confuse our spell checker, so I am wondering if the same problem is taking place here. The first and second lines of the comment might be seen as opening and closing tags. Definitely a bug and not a feature. |
zen is the art of being at one with the two'ness |
 |
|
|
Toni Schilling
New Member
Germany
3 Posts |
Posted - Mar 11 2010 : 04:44:44 AM
|
Hi, seems the tokenizer/parser has some more problems.
Try this ...
OK:
/* public: void test_nr<N >(); using the current source line number.
*//*
* Implement your test case imediately after thhe macro.
*/
NOT OK:
/*
* public: void test_nr<N >(); using the current source line number.
*//*
* Implement your test case imediately after thhe macro.
*/
OK:
/*
* public: void test_nr<N >(); using the current source line number.
*/ /*
* Implement your test case imediately after thhe macro.
*/
OK:
/*
* public: void test_nr<N >(); using the current source line number.
*/ //
/* Implement your test case imediately after thhe macro.
*/
NOT OK:
/*
* public: void test_nr<N >(); using the current source line number.
*///
/* Implement your test case imediately after thhe macro.
*/
|
|
|
|
feline
Whole Tomato Software
United Kingdom
18947 Posts |
Posted - Mar 12 2010 : 12:59:09 PM
|
I am seeing the same effect here. Thank you for the clear description.
case=40874
This looks like a separate problem, so I have put in a separate bug report for this. Hopefully you don't have to many problem comment blocks like this in your code base. |
zen is the art of being at one with the two'ness |
|
|
|
AdrianS
Senior Member
Canada
30 Posts |
Posted - Mar 13 2010 : 09:42:11 AM
|
I'm not sure if this is related. If I have the following in a CPP file, it underlines correctly.
/*
sdfjksdf
adshjkjh
*/
However, if the first line contains a period and following text, the underlines don't work, e.g.
/*
sdfjksdf.sdakj
adshjkjh
*/
Also, scrolling down slightly will make the underline on the second line appear.
VA 1814, VS2005 on Vista |
|
|
|
Toni Schilling
New Member
Germany
3 Posts |
Posted - Mar 15 2010 : 05:51:52 AM
|
> Hopefully you don't have to many problem comment blocks like this ...
No problem! Sometimes I use VA spell checker for quick lookup.
To safe the time to change to http://leo or so, I type right in the source I've currently open
... and oops!
I thought somebody could be interested. |
|
|
|
feline
Whole Tomato Software
United Kingdom
18947 Posts |
Posted - Mar 15 2010 : 3:24:42 PM
|
| AdrianS this looks like it is by design. With the dot on the line, the first like looks more like code. Having VA underline every "spelling error" in commented out code is going to get quite wearing quite fast. |
zen is the art of being at one with the two'ness |
|
|
|
Habi
New Member
4 Posts |
|
|
feline
Whole Tomato Software
United Kingdom
18947 Posts |
Posted - Mar 29 2010 : 5:07:22 PM
|
Agreed, my mistake. This also looks like it is covered by the new bug report:
case=41543 |
zen is the art of being at one with the two'ness |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Aug 04 2010 : 5:49:59 PM
|
| case=29867 and case=41543 are fixed in build 1829 |
Whole Tomato Software, Inc. |
|
|
| |
Topic |
|
spell check accidentally off?
