ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Google+ ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

Programming Topics or Design of applications and programs or Overload Journal #118 - December 2013

Options:
View Article Map
View Archives
All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Other
Code Critique Competition 103
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 28, #6 - January 2017 ]
Code Critique Competition 105
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 29, #2 - May 2017 ]
Code Critique Competition 106
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 29, #3 - July 2017 ]
Code Critique Competition 107
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 29, #4 - September 2017 | Student Code Critiques from CVu journal. ]
Code Critique Competition 110 Part II
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 30, #1 - March 2018 | Student Code Critiques from CVu journal. ]
Code Critique Competition 111
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 30, #2 - May 2018 | Student Code Critiques from CVu journal. ]
Code Critique Competition 112
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 30, #3 - July 2018 | Student Code Critiques from CVu journal. ]
Code Critique Competition 115
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 30, #6 - January 2019 | Student Code Critiques from CVu journal. ]
Code Critique Competition 92
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 27, #1 - March 2015 | Student Code Critiques from CVu journal. ]
Code Critique Competition 93
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 27, #2 - May 2015 ]
Code Critique Competition 95
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 27, #4 - September2015 ]
Code Critique Competition 96
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 27, #5 - November 2015 ]
Code Critique Competition 99
Description : Set and collated by Roger Orr. A book prize is awarded for the best entry.
Category: [ Programming Topics | CVu Journal Vol 28, #2 - May 2016 ]
[ References | Paradigms | Programming ] Code Generation Network
Description : This has a database of code generation tools and also articles and interviews on CG approaches.
Added on : 21 October 2007 13:34:24 +01:00
Code in Comments
Description :

We have all seen comments in source files which look more like executable code than documentation.

The first line in the body of the for loop below is such a comment: you might expect to be able to remove the leading slashes and have code which compiles and runs, but functions slightly differently.

What did the author of this comment intend?

Example 0

for (Surfaces::iterator sf = surfaces.begin();
     sf != surfaces.end();
     ++sf) {
  // std::cout << "Drawing: " << *sf << "\n";
  sf->draw();
}

OK, I’m being disingenuous. I’m aware that the comment isn’t really a comment, it’s commented-out code. And, like any tolerant and capable programmer, by examining the surrounding context I can guess why this code has been commented out.

This article examines how to comment out code, then describes various problems which lead to code being commented out, before finally arguing that there’s often a better solution to these problems.


Source : Hand entered.
Category: [ Programming Topics | CVu Journal Vol 16, #1 - Feb 2004 ]
Code Rot
Description : Maintaining code is vital to keep it working. Tom Guest explores what happens when you neglect it.
Category: [ Programming Topics | Overload Journal #92 - August 2009 ]
Come Code With Me
Description : Alan Griffiths outlines an Open Source project and invites contributions.
Category: [ Programming Topics | CVu Journal Vol 28, #2 - May 2016 ]
Comment on “Problem 11”
Description :

The first step here in finding problems in the code is to identify the problem the code is trying to solve. The discussion in the C Vu article is basically about curiosities in the way in which the C++ standard library std::istream is defined, but I will make the perhaps unwarranted assumption that what the problem the code is really about is not the uses of std::istream, but rather, more generally, how to write a read routine that can effectively and safely capture data from an input stream. Actually as the first problem below illustrates neither of these issues can be effectively addressed without the other.


Category: [ Programming Topics | CVu Journal Vol 16, #1 - Feb 2004 ]

  |<   <   1   2   3   4   5   6   >   >|
Sort by Date Title