![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to rex.query CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Research Unix] / researchv10dc / cmd / f2c|
Return to rex.query CVS log | Up to [Research Unix] / researchv10dc / cmd / f2c |
1.1 root 1: From uunet.UU.NET!aussie!rex Wed Nov 22 12:22:10 EST 1989
2: Received: from aussie.UUCP by uunet.uu.net (5.61/1.14) with UUCP
3: id AA15817; Wed, 22 Nov 89 22:00:30 -0500
4: Date: Wed, 22 Nov 89 12:22:10 EST
5: From: [email protected] (Rex Jaeschke)
6: Subject: Next Electronic Poll for Journal
7: Message-Id: <8911221222.18.UUL1.3#[email protected]>
8: To: [email protected]
9: Cc: [email protected]
10:
11: Electronic Poll #3 - December 1989
12:
13: Occasionally, I'll be conducting polls via electronic mail and
14: publishing the results in the Journal of C Language Translation.
15: (Those polled will also receive an e-mail report on the results.)
16:
17: ALL RESPONSES WILL BE CONFIDENTIAL AND NO COMPANIES OR INDIVIDUALS
18: WILL BE IDENTIFIED WITHOUT THEIR PERMISSION.
19:
20: Please answer the following questions for your current or planned C
21: implementation(s). Add extra comments as you like plus suggestions for
22: future poll questions. If you are not an implementer, answer as you
23: see fit.
24:
25: [Please reply to uunet!aussie!rex. My DOS version of uucp doesn't
26: seem to have a better way to automate answers from a distribution
27: list, sorry.]
28:
29:
30: 1. How do you define NULL? Is the null constant pointer actually
31: represented as all-bits-zero? What different internal pointer
32: representations do you support?
33:
34: ____________________________________________________________________
35: ____________________________________________________________________
36: ____________________________________________________________________
37: ____________________________________________________________________
38:
39: 2. Assuming you implement most of the goodies required/defined by
40: ANSI~C, how important is provable ANSI-conformance to your market
41: place? Not at all, somewhat, absolutely necessary.
42:
43: ____________________________________________________________________
44: ____________________________________________________________________
45: ____________________________________________________________________
46: ____________________________________________________________________
47:
48: 3. Do you have a home-grown or commercial validation suite? If so,
49: which?
50:
51: ____________________________________________________________________
52: ____________________________________________________________________
53: ____________________________________________________________________
54: ____________________________________________________________________
55:
56: 4. Is POSIX conformance an issue for you? What about IEEE support?
57:
58: ____________________________________________________________________
59: ____________________________________________________________________
60: ____________________________________________________________________
61: ____________________________________________________________________
62:
63: 5. What do you see as the biggest shortcoming of the ANSI~C
64: Standard, as a language standard or in some missing functionality (in
65: the library or preprocessor, for example)?
66:
67: ____________________________________________________________________
68: ____________________________________________________________________
69: ____________________________________________________________________
70: ____________________________________________________________________
71:
72: 6. Do you or will you implement long double with a different
73: representation than double? If so, will that make three different
74: floating-point representations or are float and double mapped the
75: same?
76:
77: ____________________________________________________________________
78: ____________________________________________________________________
79: ____________________________________________________________________
80: ____________________________________________________________________
81:
82:
83:
84: Thanks for your input. I'd like your responses by January 12 please.
85:
86: Rex
87:
88: ----------------------------------------------------------------------------
89: ******** NEW POSTAL ADDRESS EFFECTIVE OCT 16th
90: ----------------------------------------------------------------------------
91: Rex Jaeschke | C Users Journal | Journal of C Language Translation
92: (703) 860-0091 | DEC PROFESSIONAL | 2051 Swans Neck Way
93: uunet!aussie!rex | Programmers Journal | Reston, Virginia 22091, USA
94: ----------------------------------------------------------------------------
95: Convener of the Numerical C Extensions Group (NCEG)
96: ----------------------------------------------------------------------------
97:
98:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.