C++0x Working Draft (n2798)

Studying Working Draft of C++0x (n2798), I am waiting for implementations based on the C++0x standard.

Boost 1.37 installed

Boost 1.37 installed

bjam --toolset=msvc-7.1 link=static,shared release debug stage

This method is same as the installation of Boost 1.36.
But, I encountered a trouble on VC7.1. The VC7.1 says

"fatal error C1055: compiler limit : out of keys"

in boost's source.
This result, I turn off /GM (edit continue) and change programming databese from /ZI to /Zi.

I maybe use VC9, as the VC9 has not been bad nowadays. I feel that VC9 is same good or better than VC7.1sp1 or VC8sp1.

S60 instllation memo

• Perl 5.6.1
• S60 3rd Ed. FP1
• Carbide.c++ 1.3

I grant write access parmission to following;

• C:/Symbian/9.2/S60_3rd_FP1/epoc32
• c:/Symbian/carbide/workspace

If the write access parmission is nothing, Carbide can not build any. At first, cpp.exe of Gcce aborted.

I make console example, but mwldsym2.exe says that '/Symbian/9.2/S60_3rd_FP1/epoc32/include/stdapis' is not found. I do not find the 'stdapis' directory but the directory 'Symbian/9.2/S60_3rd_FP1/epoc32/include/libc' exists at the same position and required headers exist in the 'libc'. I change SYSTEMINCULDE from 'stdapis' to 'libc', then the error on stdapis is resolved.

I can not build yet. The build has a more error, '/Symbian/9.2/S60_3rd_FP1/EPOC32/RELEASE/WINSCW/UDEB/libc.lib not found'. I can not found libc.lib in the '/Symbian' with grep and am trying to resolve the problem.

Brainf*ck

I wrote the Brainf*ck interpreter in C++ to teach programming.

How too simple the Brainf*ck spec, I amazed. The interpreter's source consists of less than 200 lines.

VC project down converter

• VC8.0 -> VC7.1 @ Code Project
• VC7.1 -> VC7.0 @ Code Project
• VC7.0 -> VC6.0 @ Code Project

Boost 1.36 installed

bjam --toolset=msvc-7_1 link=static,shared release debug stage

This method is same as the installation of Boost 1.35.
No matter, now.

Boost 1.35 installation memo

bjam --toolset=msvc-7_1 link=static,shared release debug stage

I copied all libraries and DLLs to libs directry. Then, I renamed the libraries from "libboost_unit_test_framework-vc-xx" to "libboost_unit_test_framework-vc71-xx" because projects of mine occurs link error on libboost_unit_test_framework. More cool solution may be...

Stdout and Stderr Redirection on Windows

On Linux with bash, I log both stdout and stderr out by following method

$> foo &> out.txt

But, cmd on Windows does not support the method.

On Windows you can use following method

C:\> (foo.exe 2>&1) > out.txt

"2>" means redirection from stderr(2). So, ">" equals "1>" and the '1' means stdout(1). If you want to log stdout and stderr to each file, you can use following command.

C:\> foo.exe > out.txt 2> err.txt