From: Clinton Bunch <cdb_zsh@zentaur.org>
To: zsh-workers@zsh.org
Subject: Re: ANSI C standard of zsh
Date: Sat, 23 Mar 2024 16:26:06 -0500 [thread overview]
Message-ID: <50d25960-4789-42af-8105-51a364325903@zentaur.org> (raw)
In-Reply-To: <64761-1710348596.938223@kqf9.hufK.7DeO>
On 3/13/2024 11:49, Oliver Kiddle wrote:
> Bart Schaefer wrote:
>> On Tue, Mar 12, 2024 at 2:44 PM Clinton Bunch <cdb_zsh@zentaur.org> wrote:
>>> 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.
> No objections from me. Replacement wording would be welcome. We're using
> string pasting (##) in quite a few places despite that being "not
> available".
>
Here is my first cut at replacement wording for the first two paragraphs
of the C coding style section:
The primary language is standard C and modern versions of Zsh assume at
least the 1999 standard is available. While much of the code is written
to be compatible with older C standards, it has been decided that
maintaining compatibility with those standards has become too limiting
and is not necessary for even legacy (though not necessarily vintage)
systems.
If you wish to use features not present in the ANSI C 99 standard, there
are preprocessor macros to provide safe access to some of these. Always
use the macros if you want to use these facilities.
next prev parent reply other threads:[~2024-03-23 21:27 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
2024-03-13 4:22 ` Bart Schaefer
2024-03-13 16:49 ` Oliver Kiddle
2024-03-23 21:26 ` Clinton Bunch [this message]
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=50d25960-4789-42af-8105-51a364325903@zentaur.org \
--to=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).