Creative Constant Development Workgroup - c++

Visual Studio 命令提示字元 (2010)

cjj — Tue, 01 May 2012 01:41:00 +0000

Visual Studio 2010 Express提供了一個簡單的C++編譯環境：『Visual Studio 命令提示字元 (2010)』。
開啟後的終端機環境中可以用『cl』命令來編譯連結一般的C++程式。如：

cl hello.cpp

而glut的程式（在glut有正確安裝後）也可以直接編譯。
不過如果要編譯WIN32的程式，在命令列則要加上kernel32.lib，user32.lib，gdi32.lib等額外的程式庫以供連結：

cl hello-win.cpp kernel32.lib user32.lib gdi32.lib /FeHelloWin.exe

Tags:

c++

gltk, a C++ widget library built on GLUT

cjj — Thu, 15 Sep 2011 07:03:00 +0000

gltk is a C++ Widget library built on GLUT. The API of gltk is modeled after gtkmm, the C++ interface of the GTK+ library. The implementation of gltk was inspired by GLUI. By building on GLUT, the library is readily ported to platforms where GLUT (or FreeGLUT) is available. These include Linux, Windows, and Mac OS X.

A loose goal of gltk is to be API compatible with gtkmm, where people can, ideally, replace the Gtk namespace by gltk and have their programs compile and run on platforms where gtkmm is not available. Under the limitation of GLUT, such goal can only be filled partially. In reality, this project only aims for a close approximation to the most commonly used part of the API, so the author does not have to rewrite his existing gtkmm codes to make his programs portable with GLUT.

Following gtkmm, the communication between objects in the library is provided by the signal-slot API of libsigc++. While libsigc++ is readily ported to a wide range of platforms, to minimize the prerequisites of gltk, a very limited, in-house substitute of libsigc++, under the same sigc namespace, is provided in the header sigc.hh with the aim of making it source-compatible with libsigc++. The users of the library may replace sigc.hh with the real libsigc++ when it's available to gain flexibility and performance.

Tags:

gltk

c++

Indent style for my C++ coding

cjj — Sat, 20 Aug 2011 23:42:00 +0000

I prefer to indent my code with TABs. Some people do not like that because a TAB can represent different amount of spaces in different editors or viewers. However, I like TABs for their semantic meaning of levels of grouping. How a code editor or viewer displays this grouping information should be left to the liking of its user. And, using two spaces (or four) is just wasting an extra character when we can just set the TAB size to 2 (or 4). I also favor compactness and readability. It's desirable to make the code visually shorter as long as it remains readable. Overly loose formatting can pose an obstacle to the concentration of thought just like that overly tight formatting can also trap and tangle the flow of thought.

Following is a list of styling choices that I adopt for my C++ coding.

One variable per line of declaration.
Cuddle up while but not else.
No line break in the declaration of a function.
No space between function name and parenthesized argument list.
Colon : is space-cuddled and each inheritance starts on a newline in a class definition.
No space before comma , or semicolon ;, after left parenthesis (, and before right parenthesis ).
Comma , and semicolon ; in for-statement are spaced after.
Left brace { stands alone with the same level and on a newline for definitions of classes and functions.
Left brace { is space-cuddled and followed by a newline in a compound statement.
Right parenthesis always starts on a newline.
Colon : is space-cuddled and each base and member constructor starts on a newline in a constructor definition.
Labels are single-spaced to the left edge.
Class sectioning (private:, protected:, and public:) is on the same level as the class definition.
Operators are spaced before and after with operands or parenthesized expressions.

Tags:

c++

the new C++ standard, multidisciplinary approach

cjj — Tue, 16 Aug 2011 11:09:00 +0000

C++0x was approved by ISO. It adds a great amount of new features to an already-rich language. This very fact has drawn some criticism. And, yet there are still unsatisfied demands for features.

Just like natural languages facilitate thought and communication. Programming languages facilitate implementation of software models. An overly-rich tool places burden on the mastering of its domain but removes limitations on what models can be easily adopted to solve a problem. So, I think it's not a good news if you want to be a guru of the language. But, it is certainly nice if you have specific software problems to solve.

Tags:

c++