Not really -- a tautology is something that's inescapably
true based on the definitions of terms involved. OTOH, I
agree that this is somewhat similar. It's a circular
problem that C++ programmers don't use it that way, so
there's no tutorials for using it that way, so nobody
uses it that way, etc.
Yes, the average programmer will grab a Perl-style
language to manipulate strings. That doesn't mean C++ can't compete with
those languages in this space.
True -- but quite a bit of it is sufficiently specific
that it goes a bit beyond "manipulate strings" and into
subjects that aren't really very meaningful, at least as
stated.
[ ... ]
This is "language X for Y users" territory. If I know Perl, the first thing
that pops to mind when I have that problem is the -i switch. So leading me
from there to a clean and high-level C++ solution would be very useful and
helpful. Especially to rescue me from Perl!
It might be meaningful in that context, but simply as a
C++ cookbook, it's not meaningful at all.
The effect here should work like a "permuted index" at the end of a huge
reference book.
I'm not sure whether you're saying that's the program
you're trying to write, or whether you're saying that's
the basic intent of the web site...
Execution speed isn't the only reason to use C++.
True -- but most of the other purposes are even less
interesting. Just for example, I have precisely zero
interest in creating a CGI script (in any language) to
allow people to manipulate ACLs on the files on my
machine. The difference between C++ and PERL is
irrelevant here -- I don't want it happening regardless
of language.
I can see a situations where using C or C++ for CGI can
be useful. Just for one example, Comeau's online C++
compiler. There are certainly a lot more were a bit of
CGI acts as little more than a front end to some large
piece of software that may well be written in C or C++
(e.g. talking to a SQL database).
The question in my mind, however, is what exactly is
unique to CGI in this scenario -- if memory serves, CGI
basically says you receive a couple of environment
variables as input, and write something like an HTTP
packet on standard output.
I guess what I'm trying to say is that I can't think of
much that's unique about doing it in C++ vs. anything
else. At least to me, it seems like pretty basic
application of everyday programming techniques.
