From: Bart Schaefer <schaefer@brasslantern.com>
To: Clinton Bunch <cdb_zsh@zentaur.org>
Cc: zsh-workers@zsh.org
Subject: Re: ANSI C standard of zsh
Date: Tue, 12 Mar 2024 21:16:47 -0700 [thread overview]
Message-ID: <CAH+w=7bARMgj=fo-JkFAWEGYR9DU4jib8oDkPUk+enT_reeF-A@mail.gmail.com> (raw)
In-Reply-To: <4da53188-feb2-42d2-9294-899715991be1@zentaur.org>
On Tue, Mar 12, 2024 at 2:44 PM Clinton Bunch <cdb_zsh@zentaur.org> wrote:
>
> I was looking at the development guide and saw this:
>
> The primary language is ANSI C as defined by the 1989 standard, but the
> code should always be compatible with late K&R era compilers ("The C
> Programming Language" 1st edition, plus "void" and "enum"). There are
> many hacks to avoid the need to actually restrict the code to K&R C --
> check out the configure tests -- but always bear the compatibility
> requirements in mind. In particular, preprocessing directives must
> have the "#" unindented, and string pasting is not available.
>
> 5.9 does not compile with gcc's c89 on EL 8 or 9 (Rocky specifically).
> I intend to test FreeBSD and Solaris as well, but haven't yet.
>
>
> I will point out the C99 standard is now a quarter century old. I propose that we update the development guide to remove the bit about the 1989 standard (much less K&R compatibility) since it is no longer true, and I personally question if it even makes sense as a goal 30+ years in to development.
next prev parent reply other threads:[~2024-03-13 4:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 21:44 Clinton Bunch
2024-03-13 1:50 ` Clinton Bunch
2024-03-13 4:16 ` Bart Schaefer [this message]
2024-03-13 4:22 ` Bart Schaefer
2024-03-13 16:49 ` Oliver Kiddle
2024-03-23 21:26 ` Clinton Bunch
2024-03-25 23:47 ` Oliver Kiddle
2024-03-26 0:32 ` Clinton Bunch
2024-03-26 23:16 ` Clinton Bunch
2024-03-28 9:16 ` Jun T
2024-03-28 12:29 ` Clinton Bunch
2024-04-04 0:00 ` Vincent Lefevre
2024-04-04 22:57 ` Clinton Bunch
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='CAH+w=7bARMgj=fo-JkFAWEGYR9DU4jib8oDkPUk+enT_reeF-A@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=cdb_zsh@zentaur.org \
--cc=zsh-workers@zsh.org \
/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).