Magnus Manske wrote:
*If* we decide to work on a Phase IV (one of my
favourite movies BTW), I
think we should go for C++. Two main reasons:
- Probably the fastest way to work with arrays of char (=plain text),
which is most of the internal working of a wiki software
Although you're probably right that C++ is very fast in terms of
handling of character arrays, I'm not sure this miniscule speed benefit
rectifies using a language that isn't UTF-8 aware. Perl 5.8 onwards
understands UTF-8 and can work with it internally, i.e. in its own C
code, so it shouldn't be significantly slower.
- Real OOP, in contrast to the PHP-class jokes.
That would be one reason I would greatly agree with you.
The main reason *not* to use C++ is that I don't
know how to turn such a
program into an apache module. Help on that would be appreciated.
I don't know that either. The only two ways of using a compiled binary
in Apache that I know of would be either to set it as a handler for a
filename extension, or to call it using CGI. Both methods are
inacceptable because they create a new process for each HTTP request.
I've never heard of other web software written in C++ (apart from the
*actual* webserver, Apache, of course). Not that I mind Wikipedia being
an oddball in that respect, but if nobody did this before, maybe that's
a sign it might not be a good idea.
Maybe we should write a whole new webserver (just joking).
Timwi