N
Netocrat
[...]Mark B said:
So I went. And I looked. And I corrected a few silly stupid problems
[a]nd uncritical praise ... it was written by people who really, really
don't understand what it's about.
No, if we're going to have a C FAQ wiki, let's have a good one, that
starts from a solid base
So what should the content of a clc wiki be?
A general FAQ list is obvious and, assuming that we gain Steve's
permission to start from the current FAQ contents, is a good base. I've
made some other suggestions on the planning wiki:
* supportable and representative clc views (e.g. that casting should
be avoided where possible - this is already part of the faq from memory;
gets should not be used; the definition of lvalue is broken in C99)
* more variable representative clc views (e.g. style issues); this content
may include various alternatives and their pros and cons
* opinion pieces (e.g. on a proposed change/addition to the standard)
* different ways to solve a problem and their pros and cons (e.g. overflow
checking on integer arithmetic)
It needn't duplicate content such as that in the wikipedia article, which
although it may have a bias, is not wildly inaccurate. It makes sense for
wikipedia to be the primary source for communally-maintained encyclopedic
knowledge. The clc wiki would be the source to consult for peer-reviewed
expert knowledge/advice/opinion on portable, standard C.
The current FAQ structure i.e. sectioned and numbered by question - can be
imported into the wiki with some work (I've put up a demonstration
on the planning wiki at
http://clc.flash-gordon.me.uk/wiki/Category:FAQ_top_level) - probably a
reasonably sophisticated script could automate it.
Whether all additional content should be fit into that structure is an
open question, but it seems reasonable given the full-text search
functionality.