Comments on: Six language-independent ways to write better code http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/ Tue, 07 Feb 2012 12:30:29 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: dr.vladyslav http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-95260 dr.vladyslav Wed, 16 Mar 2011 20:59:02 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-95260 Excellent article. It opens eyes on programming prominent aspects. This article should be placed the first in programming books Thank you very much. Excellent article. It opens eyes on programming prominent aspects. This article should be placed the first in programming books

Thank you very much.

]]> By: royboy007 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-95220 royboy007 Mon, 28 Feb 2011 17:03:50 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-95220 first how do i make a dicusion second can you teach how to make hacks and stuff like hacks for games p.m me thanks nice website first how do i make a dicusion second can you teach how to make hacks and stuff like hacks for games p.m me thanks nice website

]]> By: tobi http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-81024 tobi Sat, 20 Mar 2010 11:43:55 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-81024 Write any program to solve the algorithm below: ALGORITHM= void bubble(int*3 in+n) int hold,j,passj int switched=TRUEj for(pass =oj pass<n-1$$ switch= x(j+1) x(j=1)=holdj Write any program to solve the algorithm below:
ALGORITHM= void bubble(int*3 in+n) int hold,j,passj int switched=TRUEj for(pass =oj pass<n-1$$ switch= x(j+1) x(j=1)=holdj

]]> By: programuotojo savait? #1 | kran.lt http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-68964 programuotojo savait? #1 | kran.lt Thu, 24 Sep 2009 17:30:46 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-68964 [...] 6 universal?s patarimai tam, kad pagerinti kodavimo stili?. Patarimai elementar?s, bet ver?iantys susim?styti; [...] [...] 6 universal?s patarimai tam, kad pagerinti kodavimo stili?. Patarimai elementar?s, bet ver?iantys susim?styti; [...]

]]> By: galanga http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-25837 galanga Mon, 01 Sep 2008 20:44:03 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-25837 Very good post, I wish that all the programmers in the world will one day try to respect those guidelines. The conclusion is really a must. I only have one comment : the title "Don’t use magic numbers" and the use of the expression "magic numbers", because for me a "magic number" is a specific number (as 0xAB12CD89) used to check a structure of data in memory (for example a hard drive partition structures start) to prevent as much as possible to interpret corrupted data (which often leads to coredump due to overflow, when using length fields in the corrupted data). As the first sentence says in your paragraph, what you are talking about, for me, is called "hard-coded numbers/values" (in French, as I am, "valeurs en dur dans le code"). Very good post, I wish that all the programmers in the world will one day try to respect those guidelines. The conclusion is really a must.

I only have one comment : the title “Don’t use magic numbers” and the use of the expression “magic numbers”, because for me a “magic number” is a specific number (as 0xAB12CD89) used to check a structure of data in memory (for example a hard drive partition structures start) to prevent as much as possible to interpret corrupted data (which often leads to coredump due to overflow, when using length fields in the corrupted data).

As the first sentence says in your paragraph, what you are talking about, for me, is called “hard-coded numbers/values” (in French, as I am, “valeurs en dur dans le code”).

]]> By: language independent ways to write better code « Try your best, man http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-113 language independent ways to write better code « Try your best, man Wed, 18 Jul 2007 14:47:38 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-113 [...] 18th, 2007 by hanxiaogang On his site learncpp.com, alex gives a post on six ways to write better [...] [...] 18th, 2007 by hanxiaogang On his site learncpp.com, alex gives a post on six ways to write better [...]

]]> By: Gwyn Fisher, CTO Klocwork http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-73 Gwyn Fisher, CTO Klocwork Tue, 03 Jul 2007 14:47:42 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-73 Great summary. Most, if not all, of the issues that you bring up are handled by prevalent static analysis tools (disclaimer: such as the one my company sells). Static analysis in this context can be thought of as taking off where the compiler stops, i.e. evaluating the function of the code, not just its syntactical (and surface semantic) correctness. I encourage you and your readers to check out the various tools available in the space -- search wikipedia for static analysis and you'll find links to the most popular ones (of course, I'd love it if you checked out Klocwork first! ;p). In summary, C++ continues to be a complex language to master, but there are tools out there that can act as the "guy looking over your shoulder" pointing out what you're missing, or when you're applying a potentially damaging semantic or side-effect. Great summary. Most, if not all, of the issues that you bring up are handled by prevalent static analysis tools (disclaimer: such as the one my company sells). Static analysis in this context can be thought of as taking off where the compiler stops, i.e. evaluating the function of the code, not just its syntactical (and surface semantic) correctness. I encourage you and your readers to check out the various tools available in the space — search wikipedia for static analysis and you’ll find links to the most popular ones (of course, I’d love it if you checked out Klocwork first! ;p).

In summary, C++ continues to be a complex language to master, but there are tools out there that can act as the “guy looking over your shoulder” pointing out what you’re missing, or when you’re applying a potentially damaging semantic or side-effect.

]]> By: Learn C++ - A tutorial and blog on C++, object-oriented design, and related topics » Eight C++ programming mistakes the compiler won't catch http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-71 Learn C++ - A tutorial and blog on C++, object-oriented design, and related topics » Eight C++ programming mistakes the compiler won't catch Mon, 02 Jul 2007 17:29:13 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-71 [...] Six language-independent ways to write better code [...] [...] Six language-independent ways to write better code [...]

]]> By: 6 language-independent ways to write better code : n ways to http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-67 6 language-independent ways to write better code : n ways to Fri, 29 Jun 2007 09:15:30 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-67 [...] via [...] [...] via [...]

]]> By: C http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/comment-page-1/#comment-63 C Thu, 28 Jun 2007 12:23:03 +0000 http://www.learncpp.com/general-programming/six-language-independent-ways-to-write-better-code/#comment-63 I agree with most of your point 1. Especially "code generically" is a sound advice. The C++ templates offer superb support for generic coding. Even though the syntax is obscure (and often compiler errors too), templates can really help in writing generic, reusable code. They even help *thinking* generically. Still, if you have a specific, one-off problem, making the solution a reusable library is a waste of time, or maybe even a source for a maintenance nightmare. Writing a good reusable library is difficult, and often it takes a couple of rewrites and revisions, plus more understanding of the problem domain than might be initially available, to make it truly usable. Now, if your fingers start itching to make a Copy/Paste of the original one-off, it obviously isn't a one-off any more, but a candidate for a reusable library. At that time it might be best to start from scratch and design the library properly, then maybe replace the original code. Not the other way round. The subnote on item #2 is funny. I'd say iii (or one of the classic alternatives i, j, k and m) is a perfect name for a loop variable. It is sensible to give better names to other variables, of course. I agree with most of your point 1. Especially “code generically” is a sound advice. The C++ templates offer superb support for generic coding. Even though the syntax is obscure (and often compiler errors too), templates can really help in writing generic, reusable code. They even help *thinking* generically.

Still, if you have a specific, one-off problem, making the solution a reusable library is a waste of time, or maybe even a source for a maintenance nightmare. Writing a good reusable library is difficult, and often it takes a couple of rewrites and revisions, plus more understanding of the problem domain than might be initially available, to make it truly usable.

Now, if your fingers start itching to make a Copy/Paste of the original one-off, it obviously isn’t a one-off any more, but a candidate for a reusable library. At that time it might be best to start from scratch and design the library properly, then maybe replace the original code. Not the other way round.

The subnote on item #2 is funny. I’d say iii (or one of the classic alternatives i, j, k and m) is a perfect name for a loop variable. It is sensible to give better names to other variables, of course.

]]>