Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: Just Wondering
Message-ID: <17139@mimsy.UUCP>
Date: 27 Apr 89 09:31:42 GMT
References: <17037@mimsy.UUCP> <12481@lanl.gov> <621@marob.MASA.COM> <1325@ns.network.com>
Distribution: na
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 29

[I do not know why, but I cannot resist...]

>In some article whose referent was deleted by faulty news software,
>Rob@raksha.eng.ohio-state.edu (Rob Carriere) writes:
>>A trained English reader does not a trained C programmer make, nor
>>vice versa.

In article <1325@ns.network.com> ddb@ns.network.com (David Dyer-Bennet) writes:
>Certainly not; however, both activities are performed using words and
>wordlike character groupings.  I maintain that it is silly for the 
>new upstart activity (programming) to establish rules that are in
>conflict with the rules of the old, established activity (reading).
>This only makes it harder to learn C programming, and causes lingering
>errors for years (or forever).

Clearly, then, if we are to make the language case-insensitive, it
should also be insensitive to alternative spellings for the same
word.  For instance:

	f()
	{
		int recognized;
		...
		recognised = token_is_ok();

After all, these mean the same thing.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris