From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Behun <marek.behun@nic.cz>
Date: Tue, 3 Nov 2020 17:30:11 +0100
Subject: [PATCH 10/10] setexpr: Add support for strings
In-Reply-To: <CAPnjgZ3SXdKaKmYCw=Q0w-JGhghAPVhwHdtG5q2dNEMNiY60Xg@mail.gmail.com>
References: <20201101211544.3579850-1-sjg@chromium.org>
 <20201101211544.3579850-11-sjg@chromium.org>
 <20201102000824.10fb538c@nic.cz>
 <CAPnjgZ3SXdKaKmYCw=Q0w-JGhghAPVhwHdtG5q2dNEMNiY60Xg@mail.gmail.com>
Message-ID: <20201103173011.08e22c11@nic.cz>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Tue, 3 Nov 2020 08:12:17 -0700
Simon Glass <sjg@chromium.org> wrote:

> Hi Marek,
> 
> On Sun, 1 Nov 2020 at 16:08, Marek Behun <marek.behun@nic.cz> wrote:
> >
> > What is the purpose of + operator on strings?
> > Can't we use setenv "${a}${b}" ?  
> 
> Yes, that does the same thing, although it is a bit clumsy.
> 
> setenv a *10
> setenv b *100
> setenv c "${a}${b}"
> 
> instead of
> 
> setexpr c *10 + *100

Hi Simon,

I don't know. It provides the same functionality that exists, but only
adds code.
Is someone really going to use this?

Marek

PS: What I think would be more useful is to add substringing
functionality into hush, so e.g. ${a:3:5}, and pattern substitions:
${parameter/pattern/string} ...