Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!cme!libes
From: libes@cme.nist.gov (Don Libes)
Newsgroups: comp.lang.c
Subject: Re: Frequently Asked Questions file will not exist
Message-ID: <4104@muffin.cme.nist.gov>
Date: 9 May 90 19:16:36 GMT
References: <1990May5.070317.11503@agate.berkeley.edu> <2550128@hpisod2.HP.COM>
Reply-To: libes@cme.nist.gov (Don Libes)
Organization: National Institute of Standards and Technology
Lines: 31

In article <2550128@hpisod2.HP.COM> decot@hpisod2.HP.COM (Dave Decot) writes:
>> I encourage people to answer questions by citing references to easily
>> accessible sources.  For example:
>> 
>> 	Q: How does malloc work?
>> 	A: See K&R2, page ...
>> 
>> 	Q: Can we add "complex" to C?
>> 	A: See JCLT, vol 1, page ...
>
>Do you really think everyone has the economic resources to keep a current
>set of JCLT around?  Subscriptions to this publication are rather expensive.

I have mixed feelings about JCLT.  It is expensive and I wish the
price was a lot lower.  However, the articles are generally excellent.
(Plus they carry no advertising.)

JCLT addresses a very clearly defined slice of C topics.  If you are
interested in these areas, it is a must.  If you personally can't
afford it, or cannot borrow a copy from your local technical library,
I must question how you got your computer (and job) without adequate
documentation.

JCLT is not for everyone.  I rarely refer people to it.  However, if
someone walked into my office and began to discuss their ideas for
modifying the C language, I would indeed expect them to have read
JCLT, otherwise they don't value their time very much.  Like I said in
my earlier message, most of this stuff has been published before.

Don Libes          libes@cme.nist.gov      ...!uunet!cme-durer!libes

Disclaimer: I have no connection with JCLT.