help-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Not to set PIPESTATUS unless necessary


From: Peng Yu
Subject: Re: Not to set PIPESTATUS unless necessary
Date: Sat, 18 May 2024 22:18:21 -0500

On Sat, May 18, 2024 at 6:19 PM Koichi Murase <myoga.murase@gmail.com>
wrote:

> 2024年5月18日(土) 22:57 Peng Yu <pengyu.ut@gmail.com>:
> > On Sat, May 18, 2024 at 5:21 AM Andreas Kähäri <andreas.kahari@abc.se>
> wrote:
> > > You would also need to take the POSIX standard's definiton of a
> pipeline
> > > into account, which I belive would trumph any dictionary's definition
> > > when it comes to implementing a Unix shell:
> > >
> > >         A pipeline is a sequence of one or more commands separated by
> > >         the control operator '|'.   [1]
> > >
> > > This is more or less the same as what you found in the bash manual,
> > > except for the extension that bash provides with |&
> >
> > In that case, the POSIX is also defective.
>
> It's not a language defect. POSIX *intentionally* includes a single
> command in the category of the pipeline as is clear from the formal
> grammar provided by POSIX, which Andreas has also quoted.
>
> > It is an impossibility that
> > one command is separated by a control operator.
>

You have to analyze each case separately. You can not justify one error by
say others do similar samethings as a convention, therefore it is not an
error. The logic is not correct.

The grammar of POSIX could stay as is except the name of “pipeline” is
wrong.

Based your logic, you could say transgender women is a woman. That is just
wrong. Transgender women is not a woman, it is something different from man
and woman. Calling transgender women as women, demanding the same rights as
women can cause all sorts of problems.

There is YouTube video on doublespeak. It is about a detailed analysis
about language corruption. You may need to have a better understanding of
serious consequences of language corruption and why it should not be
tolerated. Most technical people simply have little understanding in these
nontechnical areas.

We typically describe it in such a way even when it contains the case
> of a single element without any separator. A CSV (comma-separated
> values) file can contain a line of a single element without a command.
> HISTCONTROL is described in Bash Reference Manual as a
> "colon-separated list of values", but this includes a single value
> without any separator. The mathematical terminology `polynomial'
> includes a single term, e.g. x^2, even though it's not `poly' (i.e.
> many). There are many examples. The reason that they contain the case
> of a single element is because it is useful that way.
>
-- 
Regards,
Peng


reply via email to

[Prev in Thread] Current Thread [Next in Thread]