Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: Programming challenge
Date: Sun, 13 Dec 2020 21:35:17 -0800
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <86mtyhymp6.fsf@linuxsc.com>
References: <rqmceo$15g$1@dont-email.me> <rqme4j$2j2$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="ff5991e7e84d299f78a176558dfeb7ce"; logging-data="2201"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX186W+4rzD00tokULqe6RJNuzpSNcn4b9ZU="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:4cj0tuZz+wQFIpTK5DIhrYkkZDc= sha1:lDuDsEeJSIZFrAwnFATfqoQjZ3A=
Xref: csiph.com comp.lang.c:157261

Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:

> On Tue, 08 Dec 2020 00:04:56 +0100, jacobnavia wrote:
>
>> Here is my answer to the programming contest of Mr Rentsch.  Sorry, it is
>> just straight C, no gotos, and fairly easy to follow.  Thanks to Bart for
>> pointing me to a bug in it.  Since I haven't seen any other answers I
>> suppose I win by default...
>> Sad, it was an interesting exercise.
>
> [snip]
>
> Someone should update the CLC wiki with all these solutions.
> Could they be fit under
>   https://clc-wiki.net/wiki/K%26R2_solutions:Chapter_1:Exercise_23
> or maybe go into their own category.

I have looked at this in more detail now.  I have three main
reactions.

(1) My sense is these new solutions belong in a different
category, because the original problem (K&R chapt 1 ex 23)
was more modest.  Is it possible to create a new category
that links in some way with the existing solutions page?

(2) I don't know my way around the CLC wiki website very well
(hardly at all in fact).  It would be nice to get help from
someone who does.  Are there any administrators currently active?

(3) In any case I will not be putting any code on the wiki,
except possibly my own, to be sure I don't run afoul of the
site's copyright policy, and also out of general consideration
for others' sense of proprieties.