zsh-workers
 help / color / mirror / code / Atom feed
From: Clinton Bunch <cdb_zsh@zentaur.org>
To: zsh-workers@zsh.org
Subject: Re: Minimum POSIX standard
Date: Tue, 25 Oct 2022 20:51:16 -0500	[thread overview]
Message-ID: <e64acb46-4581-0bed-203a-be6c800318fe@zentaur.org> (raw)
In-Reply-To: <CAHYJk3SP2ofPphKd9eO4kPHRhg99725bzmo=T6USFeBCuOFo4A@mail.gmail.com>

On 10/23/2022 4:57 PM, Mikael Magnusson wrote:
> On 10/23/22, Clinton Bunch <cdb_zsh@zentaur.org> wrote:
>> What is the minimum POSIX standard modern Zsh code is intended to
>> conform to?
> As far as I'm aware, none.
>
Don't you think there should be?  The guidelines in the Development 
guide are somewhat vague and were apparently written more than 20 years 
ago.  (git log puts the first revision at 1999 and the updates seem to 
address git usage, typos, and module documentation)

Someone writing new code should have a baseline for what functions and 
types can be used without #ifdefs, autoconf tests and roll-your-own 
backup functions.  Something more recent than the C89 standard library 
with all it's flaws.  Are people still trying to get zsh 5.9 to run on 
SunOS 4 or AIX 3.25?

My personal opinion is that development should use at least the 
POSIX-1.2001 standard.  It's 20 years old.  That's surely old enough for 
any system still running.  (It's  certainly old enough that any such 
system is not supported by the vendor)



  reply	other threads:[~2022-10-26  1:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23 20:19 Clinton Bunch
2022-10-23 21:57 ` Mikael Magnusson
2022-10-26  1:51   ` Clinton Bunch [this message]
2022-10-26 20:18     ` Bart Schaefer
2022-10-26 20:39       ` Clinton Bunch
2022-10-26 20:44         ` Bart Schaefer
2022-10-26 20:48           ` Clinton Bunch
2022-10-27  7:40             ` Štěpán Němec

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=e64acb46-4581-0bed-203a-be6c800318fe@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).