zsh-workers
 help / color / mirror / code / Atom feed
From: Richard_Ohnemus@csg.stercomm.com (Richard Ohnemus)
To: zsh-workers@math.gatech.edu
Subject: Re: Code cleanup in ZLE bindings
Date: Wed, 8 May 1996 21:01:11 -0500 (CDT)	[thread overview]
Message-ID: <9605090201.AA00692@gandalf.csg.stercomm.com> (raw)
In-Reply-To: <10017.199605090037@stone.dcs.warwick.ac.uk> from Zefram at "May 9, 96 01:27:10 am"

> >I think enum is not supported by all compilers.  There is no enum in the
> >original K&R C.  Please send this patch again leaving the #define's (or
> >convince me that enum is supported by all C compilers on all Unix systems).
> 
> When I learned C, there was no ANSI standard, but there was most
> definitely enum.  I remember using it in VAX C in about 1988 -- that
> was basically K&R C plus void.  When I first read K&R, it was the first
> edition, and enum was there.
> 

The first edition of K&R, published in 1978, doesn't have enum as part of the
language. However, "The C Programmer's Handbook" published by Bell Labs in
1985 has enum. Also, the second edition of K&R, published in 1988, has this
little note (middle of page 215 in my copy): 'Enumerations are new since the
first edition of this book, but have been part of the language for some
years.'

I've used many different C compilers and it has been a long time since I've
seen one that doesn't support enumerations. So, I think it is safe to use
enum unless someone can document that enum is not supported by a compiler
on a system that is currently supported by zsh.

-- 
Richard J. Ohnemus	(Richard_Ohnemus@csg.stercomm.com)	(214) 868-5411
Sterling Commerce CSG
5215 North O'Connor Boulevard, Suite 1500
Irving, Texas  75039-3771



  reply	other threads:[~1996-05-09  2:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-08 15:30 Zefram
1996-05-08 22:55 ` Zoltan Hidvegi
1996-05-09  0:27   ` Zefram
1996-05-09  2:01     ` Richard Ohnemus [this message]
1996-05-09 13:39     ` Hrvoje Niksic
1996-05-09  0:32   ` Wayne Davison
1996-05-09  1:27   ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9605090201.AA00692@gandalf.csg.stercomm.com \
    --to=richard_ohnemus@csg.stercomm.com \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).