Help
And Possibly fix it as well?
Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
Page 1 of 1
Is there such a kind of software that will spot bad code?
Back to top
#2
- Hail Groovicus!
-
- Group: Moderator
- Posts: 9,522
- Joined: 05-June 04
- Gender:Male
- Location:Centerville, SD
Posted 25 September 2009 - 11:54 AM
Define 'bad code.' There are things like resharper for Visual Studio, JSLint for javascript, etc. but they are not going to correct the code for you since in most cases the software likely has no clue what you are trying to do. Then of course there is the compiler/interpreter that will catch syntax errors.
"Take the risk of thinking for yourself, much more happiness, truth, beauty, and wisdom will come to you that way" - Christopher Hitchens
#3
- Member
-
- Group: Members
- Posts: 46
- Joined: 17-September 09
- Gender:Male
- Location:Indianapolis - IN
Posted 25 September 2009 - 02:56 PM
Depends,
Some IDEs will correct syntax error... (such as a missing semi-column in C)
Others might underline them as microsoft word would underline some bad spelling.(Eclipse)
But since there is no way it'll know what you're actually trying to do... the answer to your question would be no.
If it existed, it would be nice though
Some IDEs will correct syntax error... (such as a missing semi-column in C)
Others might underline them as microsoft word would underline some bad spelling.(Eclipse)
But since there is no way it'll know what you're actually trying to do... the answer to your question would be no.
If it existed, it would be nice though
#4
- Bleepin Engineer
-
- Group: Malware Response Instructor
- Posts: 10,080
- Joined: 17-January 08
- Gender:Male
- Location:Cleveland, Ohio
Posted 25 September 2009 - 02:59 PM
Coverity makes some automated code analysis tools. Microsoft also has FxCop which ships with Visual Studio for all the .NET languages.
Billy3
Billy3
Look buddy, I'm an Engineer, and that means I solve problems. Not problems like "What is beauty?" .. 'cause that would fall under the purview of your conundrums of philosophy....
Twitter: @MalwareMinigun Blog: WinWrench
Students get free software through Microsoft DreamSpark
Students compete to solve world problems in the Microsoft Imagine Cup
Twitter: @MalwareMinigun Blog: WinWrench
Students get free software through Microsoft DreamSpark
Students compete to solve world problems in the Microsoft Imagine Cup
#5
- New Member
-
- Group: Members
- Posts: 11
- Joined: 17-November 09
- Location:Columbus, Ohio
Posted 19 November 2009 - 11:04 AM
Well, there probably is, however you have to ask yourself, is this really what I want.....?????
Here's the deal. If you use a "high-speed-bad-code-detector-gizmo", the question becomes
what have I learned from this....?
By going through countless iterations of the development cycle, enduring the "pain and suffering" of
trying to decipher other developers code, after awhile, (...and trust me on this one...) you
will be able to spot "bad code", in most cases, right from the start.
I know, I know, time is of the essence in some software development organizations. Got to get it fixed and back in to production. Need an answer now.
Blah, blah, blah....
But in the longterm, as painful as it is, determining what "bad code" is, and how to identify it will come from the experience of going
through the software, determining better solultions, and applying those solutions in future developments.
This is how us "old coots"
used to have to do it. Just depends on what you want and how you want to do it......
IL
Here's the deal. If you use a "high-speed-bad-code-detector-gizmo", the question becomes
what have I learned from this....?
By going through countless iterations of the development cycle, enduring the "pain and suffering" of
trying to decipher other developers code, after awhile, (...and trust me on this one...) you
will be able to spot "bad code", in most cases, right from the start.
I know, I know, time is of the essence in some software development organizations. Got to get it fixed and back in to production. Need an answer now.
Blah, blah, blah....
But in the longterm, as painful as it is, determining what "bad code" is, and how to identify it will come from the experience of going
through the software, determining better solultions, and applying those solutions in future developments.
This is how us "old coots"
used to have to do it. Just depends on what you want and how you want to do it......IL
This post has been edited by Imperious Leader: 19 November 2009 - 11:07 AM
#6
- Bleepin' Night Watchman
-
- Group: Moderator
- Posts: 7,329
- Joined: 05-December 05
- Gender:Not Telling
- Location:Right behind you
Posted 21 November 2009 - 11:37 PM
)
Help us help you. If HelpBot replies, you MUST follow step 1 in its reply so we know you need help.
Boredom Software Stop Highlighting Things
Boredom Software Stop Highlighting Things
Share this topic:
Page 1 of 1