From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-patches@cygwin.com
Subject: Re: [EXTERNAL] Re: [PATCH] Cygwin: spawn: Treat empty path as the current directory.
Date: Thu, 30 Jun 2022 13:03:43 -0600 [thread overview]
Message-ID: <f766aa3a-6bca-5d6b-50c9-316e87816ea1@SystematicSw.ab.ca> (raw)
In-Reply-To: <DM8PR09MB7095DDCF46700AB235A53717A5BA9@DM8PR09MB7095.namprd09.prod.outlook.com>
On 2022-06-30 12:35, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via
Cygwin-patches wrote:
>> However, use of this feature is deprecated, and POSIX notes that a
>> conforming application shall use an explicit pathname (e.g., .) to
>> specify the current working directory.
> Since "SHALL" does not mean "MUST", I think this patch is correct.
It appears you may be confusing POSIX's (1.5 Terminology)
*shall* (mandatory) and *should* (recommended):
"*SHALL*
For an implementation that conforms to POSIX.1-2017, describes a feature
or behavior that is mandatory. An application can rely on the existence
of the feature or behavior.
For an application or user, describes a behavior that is mandatory.
*SHOULD*
For an implementation that conforms to POSIX.1-2017, describes a feature
or behavior that is recommended but not mandatory. An application should
not rely on the existence of the feature or behavior. An application
that relies on such a feature or behavior cannot be assured to be
portable across conforming implementations.
For an application, describes a feature or behavior that is recommended
programming practice for optimum portability."
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-06-30 19:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 12:44 Takashi Yano
2022-06-30 15:45 ` Ken Brown
2022-06-30 18:35 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-06-30 19:03 ` Brian Inglis [this message]
2022-06-30 19:04 ` Takashi Yano
2022-07-01 1:16 ` Ken Brown
2022-07-01 23:31 ` Takashi Yano
2022-07-02 1:32 ` Ken Brown
2022-07-04 8:37 ` Corinna Vinschen
2022-07-04 23:05 ` Ken Brown
2022-07-05 4:54 ` Takashi Yano
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=f766aa3a-6bca-5d6b-50c9-316e87816ea1@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).