Solved

Statically detectable features of C++

Posted on 2004-05-01
8
184 Views
Last Modified: 2010-04-01
Hi all,

I am writing a programming standard for a project i am just about to start. I was just after all the possible statically detectable features of C++ to be considered when writing programming standards to check if I have included all important ones. Thanx,
        Andy
0
Comment
Question by:acrxx
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 39

Expert Comment

by:itsmeandnobodyelse
Comment Utility
>> statically detectable features of C++

I don't know what do you want to say with that expression.

The problem is that the Compiler checks C++ syntax (features). All restrictions beyond the fact that a C++ code has to be compilable are subject of your individual decision. So, you may postulate a strict hungarian name convention or insist on compliance to (new) C++ standard (both i would recommend). However, these issues are _NOT_  'statically detectable' at least not with easy means.

Regards, Alex
0
 
LVL 3

Expert Comment

by:CoolBreeze
Comment Utility
what is meant by
>> statically detectable features of C++
?

if you want to do static checking, check out this page:
http://amks0203.turkuamk.fi/msuni/Testing/Teststatic.pdf

but otherwise, it is like what itsmeandnobodyelse said, pretty much is a subject of your individual decision.
0
 

Author Comment

by:acrxx
Comment Utility
statically detectable concerns errors that can be detected without running the code
0
 
LVL 30

Expert Comment

by:Axter
Comment Utility
One way to add extra static checking is to increase the compiler warning options to the highest setting, and to also set the option to have your compiler treat warnings as errors.
Most compilers support these two features, and code is more portable when compiled with these options.
0
Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

 

Author Comment

by:acrxx
Comment Utility
Thank you for your suggestions, butI am not talking about how to detect them, I am looking for different examples of such errors
0
 
LVL 30

Expert Comment

by:Axter
Comment Utility
>>Thank you for your suggestions, butI am not talking about how to detect them, I am looking for different examples of such errors

Why would this be important if the compiler is going to catch it for you?
0
 
LVL 3

Accepted Solution

by:
CoolBreeze earned 250 total points
Comment Utility
as acrxx mentioned, statically detectable concerns errors that can be detected without running the code.
this includes logic error, includes checking for the life-time, scope, type of variables, branch flow etc.
(these are talked about in the link provided earlier)

but as what Axter said, what is important is not the errors, it is about catching them. So what we should be interested in is the various ways of catching them, compiler being one of them.

why do I say we should concentrate more on the methodology of checking instead? because a single problem can leads to many different errors. There are just too many errors to consider. Consider all the various different syntax errors, that is many. For example using an inappropriate type for variables might lead to corrupted data, or might lead to memory leak, etc.

therefore if one concentrates on getting all the different errors, it is hard to succeed. Instead, in my humble opinion, one should look at something and think : this is correct, but what can I put in the standard such that other people will not deviate from this approach which I know is right.

or if I want a more flexible standard, I would think : this is one way of doing it and I know it is correct, can't find any bugs about it. But what if they did it another way? Is there any way for me to test whether that code is just as good?
0
 
LVL 30

Expert Comment

by:Axter
Comment Utility
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

Written by John Humphreys C++ Threading and the POSIX Library This article will cover the basic information that you need to know in order to make use of the POSIX threading library available for C and C++ on UNIX and most Linux systems.   [s…
Introduction This article is the first in a series of articles about the C/C++ Visual Studio Express debugger.  It provides a quick start guide in using the debugger. Part 2 focuses on additional topics in breakpoints.  Lastly, Part 3 focuses on th…
The viewer will be introduced to the technique of using vectors in C++. The video will cover how to define a vector, store values in the vector and retrieve data from the values stored in the vector.
The viewer will be introduced to the member functions push_back and pop_back of the vector class. The video will teach the difference between the two as well as how to use each one along with its functionality.

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now