* =?iso-8859-1?q?Stephan_Br=F6nnimann?=:
Why restrict the tutorial to Windows?
You have a point. I think Mac people could benefit from a corresponding
tutorial for the Mac. On the other hand, if someone is running Linux,
then I think chances are that such a tutorial isn't needed (even though
both OS/X and Linux are *nix the kind of user and how it's used is very
different).
The reason I write for Windows is that that's what I'm best at.
The reason I think system-specific details are important in learning how
to use the tools is that there are no system-independent tools -- the
main hurdles are system-specific. The reason I think system-specific
details are important in learning how to use C++ (I've not come to that
yet...) is that doing system-specific things is a main reason for using
C++, and what C++ is traditionally used for. Otherwise one could just
as well use e.g. Java. For example, "The UNIX Programming Environment",
by Kernighan and Pike, was a great book to learn what C was all about.
Placing the language and its practical application in context -- what
to use it for, and what not.
I'd suggest to provide for each program:
+ the explaine program itself
+ compilation under Windows
+ compilation under Unix
I think compilation under Unix is pretty well covered by showing how
it's done using g++?
Of course then there should be a section that deals with the
installation of the complier and the development environment.
Is there any *nix, with the possible exception of Max OS/X, that doesn't
have a C++ compiler installed?
If you don't insist on XHTML I'll convert your document to HTML
(and later upgrade to XHTLM which I'm not familiar with
Thanks, that would be great. XHTML is just a very well-defined and
somewhat restricted form of HTML. The reasons I think XHTML could be
better for this are that (1) HTML often becomes very browser-specific,
and (2) XHTML is probably _much_ better suited for further conversion,
and (3) XHTML is the current HTML standard: the old HTML is
yestercentury's technology... ;-)