Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Ilkka Virta Newsgroups: gnu.bash.bug Subject: Re: expression evaluation problem Date: Thu, 25 Jul 2019 21:15:00 +0300 Lines: 22 Approved: bug-bash@gnu.org Message-ID: References: <5D3889D2.3090101@tlinx.org> <20190724175103.GN1218@eeg.ccf.org> <5D38A6BF.9020309@tlinx.org> <66182cdf-4448-8b49-fa65-d28ef1c64b95@iki.fi> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1564078523 7128 209.51.188.17 (25 Jul 2019 18:15:23 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash To: L A Walsh Envelope-to: bug-bash@gnu.org User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 In-Reply-To: <5D38A6BF.9020309@tlinx.org> Content-Language: en-US X-SASI-RCODE: 200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; h=subject:to:cc:references:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding; s=smtp; bh=gXHR9SP/EYKj9dd4krve5j0v40a5fwMExgt2dNHFCLg=; b=sSdRtUn8JCq1mvkBzgPtqNIA9UML2SIucrdy80vi/AzMYwTvkEVPTJPpbYR59Re8g/HY0wmJBwSXEs9MBwA2FF08Fa85SiPC8jB4clrsuGZSMZXm/DLGFAymN1cqzhlHtNpaSjteH++sXSXI0eNslJz0/6Gjp3aKcXDt9oD9PKuAZpPSbMRTYbt/RTuJBhLsyUbYZZRZmPNAu+eh5/px3N9IRWG3Xzr/5ml0kjD+jk5AROhzoKSXAWWnWynFdBKMJobbBoIVlomvtRGfZ8HPr9+68QOO+8sYJQYoBsqVYTweADpxhXgeXzxdIClpzt+HkxXo334kGLtwpBJ89oIpPw== X-detected-operating-system: by eggs.gnu.org: FreeBSD 8.x X-Received-From: 157.24.2.104 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <66182cdf-4448-8b49-fa65-d28ef1c64b95@iki.fi> X-Mailman-Original-References: <5D3889D2.3090101@tlinx.org> <20190724175103.GN1218@eeg.ccf.org> <5D38A6BF.9020309@tlinx.org> Xref: csiph.com gnu.bash.bug:15247 On 24.7. 21:43, L A Walsh wrote: > Does it improve execution time? That's more of a concern here than > readability, since it is an expression fragment, it isn't meant to be > understood > in isolation. [...] > The important part for me is whether or not it is faster to perform > 1 calculation, or 100. So which would be faster? In this case > execution speed > is more important than clarity. I consider that a 'constraint'. Shouldn't it be easy enough to measure how much restructuring that expression affects the execution speed? Also, regarding execution speed, I've been led to believe that the shell in general is rather slow, and almost any other language would be better if that is of concern. (awk, Perl, what have you.) -- Ilkka Virta / itvirta@iki.fi