|
|
researchv10 Norman
From uunet.UU.NET!aussie!rex Wed Nov 22 12:22:10 EST 1989
Received: from aussie.UUCP by uunet.uu.net (5.61/1.14) with UUCP
id AA15817; Wed, 22 Nov 89 22:00:30 -0500
Date: Wed, 22 Nov 89 12:22:10 EST
From: [email protected] (Rex Jaeschke)
Subject: Next Electronic Poll for Journal
Message-Id: <8911221222.18.UUL1.3#[email protected]>
To: [email protected]
Cc: [email protected]
Electronic Poll #3 - December 1989
Occasionally, I'll be conducting polls via electronic mail and
publishing the results in the Journal of C Language Translation.
(Those polled will also receive an e-mail report on the results.)
ALL RESPONSES WILL BE CONFIDENTIAL AND NO COMPANIES OR INDIVIDUALS
WILL BE IDENTIFIED WITHOUT THEIR PERMISSION.
Please answer the following questions for your current or planned C
implementation(s). Add extra comments as you like plus suggestions for
future poll questions. If you are not an implementer, answer as you
see fit.
[Please reply to uunet!aussie!rex. My DOS version of uucp doesn't
seem to have a better way to automate answers from a distribution
list, sorry.]
1. How do you define NULL? Is the null constant pointer actually
represented as all-bits-zero? What different internal pointer
representations do you support?
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
2. Assuming you implement most of the goodies required/defined by
ANSI~C, how important is provable ANSI-conformance to your market
place? Not at all, somewhat, absolutely necessary.
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
3. Do you have a home-grown or commercial validation suite? If so,
which?
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
4. Is POSIX conformance an issue for you? What about IEEE support?
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
5. What do you see as the biggest shortcoming of the ANSI~C
Standard, as a language standard or in some missing functionality (in
the library or preprocessor, for example)?
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
6. Do you or will you implement long double with a different
representation than double? If so, will that make three different
floating-point representations or are float and double mapped the
same?
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
Thanks for your input. I'd like your responses by January 12 please.
Rex
----------------------------------------------------------------------------
******** NEW POSTAL ADDRESS EFFECTIVE OCT 16th
----------------------------------------------------------------------------
Rex Jaeschke | C Users Journal | Journal of C Language Translation
(703) 860-0091 | DEC PROFESSIONAL | 2051 Swans Neck Way
uunet!aussie!rex | Programmers Journal | Reston, Virginia 22091, USA
----------------------------------------------------------------------------
Convener of the Numerical C Extensions Group (NCEG)
----------------------------------------------------------------------------
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.