Re: c.l.c wiki update
- From: Netocrat <netocrat@xxxxxxxxxxx>
- Date: Sat, 14 Jan 2006 13:57:10 GMT
On Sat, 14 Jan 2006 06:58:42 +0000, Richard Heathfield wrote:
> Netocrat said:
>
>> Content's more relevant and some starting content has been imported -
>> the K&R2 solutions from RJH's unmaintained site:
>> <http://clc-wiki.net/wiki/KR2_Chapter_Index>
>
> I took a quick look, and I think you've made a good job of this. (It was
> a /very/ quick look, but what I saw didn't make me think "oh deary deary
> me", so I guess that's a good sign.)
That's good to know. The changes from html to wiki markup were minor
anyhow - the wiki engine does a good job of presentation.
> I had been contemplating hoiking the whole thing over to my current
> site, but now I will gratefully not bother.
>
> Could anyone wishing to submit K&R2 exercise solutions or critiques of
> existing solutions please do so via clc-wiki.net in future? Thank you.
>
> [SFX: washes hands, a la Pontius Pilate.]
Would a scheme similar to that described in my immediately prior post
encourage you to keep your hand in? (stable version review group)
> I hope I'm right in thinking that you won't allow idiots to undo
> experts' changes.
As it stands there's nothing to prevent anyone from creating an account
and making changes. Given that there's very little traffic on the wiki
it's easy to monitor all changes though (web/RSS) - so any "idiot undos"
can be shortly reverted. I'm monitoring the site and I presume the other
wiki planners are too; more and expert monitors would be useful.
> (Steve Summit said)
>>> At any rate, let's see some more discussion about the Wiki idea!
>
> Agreed. I think this newsgroup is the right place to discuss it, too, if
> we wish to avoid the problems Wikipedia faces with quality. And it'll
> make a pleasant change from wittering on about void main. I don't know
> whether clc-wiki.net aims to restrict itself purely to portable C.
The wiki's topicality follows from comp.lang.c's - the main difference is
that longer articles are possible and it can present tangential
information such as resource lists. This is slightly unrelated, but I've
just added a "Community And Resources" category and two articles in that
category:
* <http://clc-wiki.net/wiki/Home_Pages>
if you have a c-related home-page and you post to comp.lang.c or are a
committee member, feel free to add it to this list; also if you don't
want to be listed there you can remove yourself
* <http://clc-wiki.net/wiki/Reading_And_Posting_To_comp.lang.c>
this page will be complete when Kenny McCormack and Keith Thompson agree
that it fairly describes the newsgroup.
> If it doesn't, it will need to institute an apartheid principle to make
> it abundantly clear what is portable and what is not, and discussion of
> the non-portable bits should be done elsenet.
Any non-portable code/discussion should be as incidental and clearly
demarcated as it generally is in posts to this newsgroup.
--
http://members.dodo.com.au/~netocrat
.
- Follow-Ups:
- Re: c.l.c wiki update
- From: Richard Heathfield
- Re: c.l.c wiki update
- References:
- Re: c.l.c wiki update
- From: Netocrat
- Re: c.l.c wiki update
- From: Richard Heathfield
- Re: c.l.c wiki update
- Prev by Date: Re: detect necessary #includes
- Next by Date: About retrieve an arbitrary byte among four bytes of an int.
- Previous by thread: Re: c.l.c wiki update
- Next by thread: Re: c.l.c wiki update
- Index(es):
Relevant Pages
|
