Devicetree Spec
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: devicetree spec mailing list <devicetree-spec@vger.kernel.org>
Subject: Re: Definition of "should" seems inconsistent with idea of "deprecated"
Date: Mon, 23 Oct 2023 11:32:37 +1100	[thread overview]
Message-ID: <ZTW/JU/fjdgYRkmo@zatzit> (raw)
In-Reply-To: <e86932a-f08b-e23-bf6-d8b7f688ce3@crashcourse.ca>

[-- Attachment #1: Type: text/plain, Size: 2190 bytes --]

On Sat, Oct 21, 2023 at 05:08:48AM -0400, Robert P. J. Day wrote:
> On Fri, 20 Oct 2023, David Gibson wrote:
> 
> > On Thu, Oct 19, 2023 at 07:03:56AM -0400, Robert P. J. Day wrote:
> > >
> > >   Reading DTSpec v0.4, near the beginning:
> > >
> > > "The word should is used to indicate that among several possibilities
> > > one is recommended as particularly suitable, without mentioning or
> > > excluding others; or that a certain course of action is preferred but
> > > not necessarily required; or that (in the negative form) a certain
> > > course of action is deprecated but not prohibited (should equals is
> > > recommended that)."
> > >
> > >   It seems contradictory to suggest that "should" implies
> > > "recommended" but, in the negative sense, it can also support
> >
> > I believe that by "in the negative form", it means when something says
> > "should not"..
> >
> > > "deprecated", which typically suggests something that is *not*
> > > recommended but is nonetheless acceptable.
> >
> > ..in which case being similar to "deprecated" makes sense.
> >
> > I will agree that saying "in the negative form", parenthesized,
> > amongst a cluster of interacting clauses is probably not a great way
> > of expressing this, and it might be clearer to explicitly give a
> > meaning to "should not".
> 
>   Yes, I see that I misread it somewhat and it's not as bad as I
> thought originally, but it definitely would be clearer if the concept
> of "should not" was combined with the idea of, say:
> 
>   "Should not" means that, even if a particular possibility is
> discouraged or deprecated, it is still acceptable as a viable choice.
> 
>   Or something like that. "in the negative form" is way too wordy for
> saying simply, "should not".

Yeah.  I guess it covers "shouldn't" as well, and maybe there are
other ways of negating the sense of "should" that I'm not thinking of
at the moment.  Not convinced that's a good trade off, though.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-10-23  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 11:03 Definition of "should" seems inconsistent with idea of "deprecated" Robert P. J. Day
2023-10-19 23:33 ` David Gibson
2023-10-21  9:08   ` Robert P. J. Day
2023-10-23  0:32     ` David Gibson [this message]

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=ZTW/JU/fjdgYRkmo@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=devicetree-spec@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    /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