Advertisement
Membership
Login
ACCU Buttons
Programming Topics or Overload Journal #39 - Sep 2000
Browse in : |
All
> Topics
> Programming All > Journals > Overload > 39 All of these categories |
- Options:
- View Article Map
- View Archives
Category: [ Programming Topics | Overload Journal #72 - Apr 2006 ]
Description : Links to C++ information
Added on : 11 February 2006 22:33:01 +00:00
Description : This site provides an on-line edition of the text and other material from my book "Compilers and Compiler Generators - an introduction with C++", published in 1997 by International Thomson Computer Press.
Added on : 10 February 2006 23:58:19 +00:00
Description : The Linux Cross-Reference project is the testbed application of a general hypertext cross-referencing tool. (Or the other way around.)
Added on : 10 February 2006 23:34:25 +00:00
Description : Cactus is a simple test framework for unit testing server-side java code (Servlets, EJBs, Tag Libs, Filters, ...).
Added on : 10 February 2006 22:54:23 +00:00
Description : In spite of the attention given to object-oriented development, TDD and modern testing frameworks, it is worth understanding how and why unit testing has an important role to play in general, regardless of the technologies or broader development philosophy involved. This article walks through a simple example, highlighting some of the motivation behind basic unit testing and the practices involved but without following through into TDD.
Category: [ Programming Topics | Overload Journal #68 - Aug 2005 ]
Description : Interface classes are a principle mechanism for separating a class' interface from its implementation in C++. I wrote an introduction to interface classes in a previous article. In this article, I intend to explore interface classes - and their implementation classes - further.
Category: [ Programming Topics | Overload Journal #68 - Aug 2005 ]
Category: [ Programming Topics | Overload Journal #65 - Feb 2005 ]
Description :
In this second installment of our series on GUI programming with the Qt C++ toolkit, we're going to see how to create a standard GUI application, with a menu, toolbar, status bar, and a central area.
Category: [ Programming Topics | CVu Journal Vol 16, #4 - Aug 2004 ]
Description : p>This article describes the C++ code for performing basic operations on matrices using templates.
Category: [ Programming Topics | CVu Journal Vol 16, #4 - Aug 2004 ]
Category: [ Programming Topics | Overload Journal #62 - Aug 2004 ]
Description :
There have been many languages for writing applications, but relatively few foundation platforms which support applications that are written in various different languages. We've had assembler (proprietary), then C (an ISO standard), and now we have the Common Language Infrastructure (CLI). The CLI standard is ISO/IEC 23271; the same content is also available online at http://www.ecma-international.org/publications/standards/Ecma-335.htm.
Category: [ Programming Topics | CVu Journal Vol 16, #2 - Apr 2004 ]
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 ]
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 ]
Category: [ Programming Topics | Overload Journal #58 - Dec 2003 ]