|
C++!!
ed
~"Watch your thoughts; they become your words. Watch your words they become your actions.
Watch your actions; they become your habits. Watch your habits; they become your character.
Watch your character; it becomes your destiny."
-Frank Outlaw.
|
|
|
|
|
Eclipse have some good C/C++ tools too !!!
TOXCCT >>> GEII power [toxcct][VisualCalc]
|
|
|
|
|
I don't know of any free lint tools for C++. There is of course Splint[^], but that's C only. AFAIK PC-Lint (which we use) was developed from the same ancestral code.
If you are planning to move to VS2005 there is PREfast[^], of course.
Anna
Riverblade Ltd - Software Consultancy Services
Anna's Place | Tears and Laughter
"Be yourself - not what others think you should be"
- Marcia Graesch
"Anna's just a sexy-looking lesbian tart"
- A friend, trying to wind me up. It didn't work.
|
|
|
|
|
Hello,
I don't use a tool that tells me that my variable names are wrong or something similar. No I review my code (if possible, I let someone else do that). This keeps the mind sharp and lets you think a little bit more before you write some code.
In my experiance, when you use such a tool, you try to make the tool happy. This is not always right, especially when you use an uncommon language construct.
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
Hey man, take it easy, there is nothing wrong using a tool to help one's own job
Anyway I tryed FxCop once, gives me plenty of stupid error.
Never bothered to use it again.
Maybe I will give a new go one of these day...
|
|
|
|
|
Many of the rules in FxCop are silly (naming etc.), but the globalization rules are pretty important.
string text = "This is a test.";
Thread.CurrentThread.CurrentCulture = new CultureInfo("tr-TR"); // simulate Turkish system
Debug.WriteLine(text.ToUpper());
Debug.WriteLine(text.ToUpper(CultureInfo.InvariantCulture));
This does print:
THİS İS A TEST. (note the dot above the İ)
THIS IS A TEST.
If you are using something like 'Path.GetExtension(fileName).ToUpper() == ".GIF"', it won't work on Turkish systems!
FxCop really helps to check for cases like this. In the GetExtension example, it would yield two errors: no CultureInfo specified and you can save the string allocation by using .Equals(".GIF", StringComparison.InvariantCultureIgnoreCase).
|
|
|
|
|
interesting insight...
I might probably give it a new try....
|
|
|
|
|
Super Lloyd wrote:
Hey man, take it easy, there is nothing wrong using a tool to help one's own job
I agree with that, but I don't wan't to use some tool that obstructs me from doing what I need to do. With some project, we agreed to use a naming convention. When we used together, we got numerous warning messages about the naming conventions. We turned that checking off and eventually we put the entire tool aside and started to review eachothers code.
I'll be happy to use a tool which I can modify towards my needs. I also want to automate the reporting process. That would be a great tool for my needs.
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
Bob Stanneveld wrote:
I'll be happy to use a tool which I can modify towards my needs.
If you're working with .NET, you can use FxCop...
I don't see dead pixels anymore...
Yes, even I am blogging now!
|
|
|
|
|
Can you use it for C++ to? I work with both C# and C++.
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
|
After years of programming, I no longer have simple bugs in my code. All I need is someone who can find the serious bugs for me.
My articles and software tools
|
|
|
|
|
Dude. You are funny
|
|
|
|
|
Hey, that's a code analysis tool, right?
The generation of random numbers is too important to be left to chance.
|
|
|
|
|
Given that we're responsible for LintProject[^] and Visual Lint[^] it shouldn't be a surprise that we use PC-Lint pretty extensively.
Although PC-Lint takes a little tuning to get optimum results from it, we've found it to be extremely effective at spotting little "party quirks" in our (and other people's!) code.
In some cases we've actually been able to predict the conditions that would cause a significant (and unpleasant) change in behaviour of the target app, merely by looking at the context of a simple Lint message such as a variable scope warning. The testers didn't spot it until we told them how to reproduce it...
Highly recommended.
As an aside, a little while ago we seriously looked at using CLRxLint as well, but it seems to be a product whose development has stalled.
Does anyone here have any experience of it?
Anna
Riverblade Ltd - Software Consultancy Services
Anna's Place | Tears and Laughter
"Be yourself - not what others think you should be"
- Marcia Graesch
"Anna's just a sexy-looking lesbian tart"
- A friend, trying to wind me up. It didn't work.
|
|
|
|