[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: non working code .. loop ends after one
From: |
Greg Wooledge |
Subject: |
Re: non working code .. loop ends after one |
Date: |
Thu, 2 Mar 2023 14:47:12 -0500 |
On Thu, Mar 02, 2023 at 07:41:22PM +0000, Kerin Millar wrote:
> alex xmb ratchev <fxmbsw7@gmail.com> wrote:
> > yes yes , but my argument is declare is faster .. even if for this app /
>
> $ unset -v sep; time for ((i = 0; i <= 500000; i++)); do sep='\n'; printf -v
> sep %b "$sep"; done
> real 0m3.932s
[...]
Yeah, I thought about doing that too. But then I read his next
sentences.
> i rather var-assign than printf , .. thanks
> though
> i like fancy special code ..
> i learn this way
It's clear that his *real* reason for using the slower, harder-to-read
way is because that's how he wants to do it. There are no rational
arguments that will sway him.
- Re: non working code .. loop ends after one, (continued)
- Re: non working code .. loop ends after one, alex xmb ratchev, 2023/03/01
- Re: non working code .. loop ends after one, alex xmb ratchev, 2023/03/01
- Re: non working code .. loop ends after one, alex xmb ratchev, 2023/03/01
- Re: non working code .. loop ends after one, Kerin Millar, 2023/03/01
- Re: non working code .. loop ends after one, alex xmb ratchev, 2023/03/02
- Re: non working code .. loop ends after one, Kerin Millar, 2023/03/02
- Re: non working code .. loop ends after one,
Greg Wooledge <=
- Re: non working code .. loop ends after one, alex xmb ratchev, 2023/03/03
- Re: non working code .. loop ends after one, alex xmb ratchev, 2023/03/03
Re: non working code .. loop ends after one, alex xmb ratchev, 2023/03/01
Re: non working code .. loop ends after one, Chet Ramey, 2023/03/01