Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14492
| From | Bob Proulx <bob@proulx.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Unexpected delay in using arguments. |
| Date | 2018-08-15 01:36 -0600 |
| Message-ID | <mailman.5128.1534318599.1292.bug-bash@gnu.org> (permalink) |
| References | <CAFra36j=UuqHv2Spp26ebAW0dRW+KsgNS21hZJrwuku9QUayWw@mail.gmail.com> <20180814123113518879862@bob.proulx.com> <CAFra36i8APbrP77S-v2wQgUp17bOprQtFqaYHHKqduRZuORVTA@mail.gmail.com> |
Bize Ma wrote: > > but just the same it is almost always possible > > to refactor a program into a different algorithm that avoids the need > > to enumerate so many arguments in memory. > > As you say: "almost". I still believe that to be true. Since you haven't shared what the actual task is there is no way for us to propose any counter example improvements. So "almost" is as far as I can go. Instead should I say 99.44% of the time? Since I have never come across a counter example yet? > Take a look at the Stéphane Chazelas example to convince yourself. Nothing Stéphane said changed my statement at all. It does look like bash can be more efficient with argument handling. Since, for example, dash does it. Bob
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Unexpected delay in using arguments. Bob Proulx <bob@proulx.com> - 2018-08-15 01:36 -0600
csiph-web