From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 10/10] setexpr: Add support for strings
Date: Fri, 6 Nov 2020 15:58:21 -0500 [thread overview]
Message-ID: <20201106205821.GI5340@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ0wnChBUfyP7bz66K0_LptqYu5bKVrLOqodQGnWVQ4ung@mail.gmail.com>
On Thu, Nov 05, 2020 at 10:27:25AM -0700, Simon Glass wrote:
> Hi Marek,
>
> On Tue, 3 Nov 2020 at 09:30, Marek Behun <marek.behun@nic.cz> wrote:
> >
> > 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?
>
> I don't know. Perhaps we can wait and see if anyone cares?
Sorry, does that mean this support is just speculative? Or did I
misread this part of the thread? Thanks.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201106/393c248a/attachment.sig>
next prev parent reply other threads:[~2020-11-06 20:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 21:15 [PATCH 00/10] setexpr: Correct various bugs and add tests plus string support Simon Glass
2020-11-01 21:15 ` [PATCH 01/10] test: Add some tests for setexpr Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 02/10] command: Add constants for cmd_get_data_size string / error Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 03/10] setexpr: Add explicit support for 32- and 64-bit ints Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 04/10] test: Add some setexpr regex tests Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 05/10] setexpr: Split the core logic into its own function Simon Glass
2020-12-02 21:22 ` Tom Rini
2020-11-01 21:15 ` [PATCH 06/10] setexpr: Add some tests for buffer overflow and backref Simon Glass
2020-12-02 21:23 ` Tom Rini
2021-01-17 22:52 ` CRASH caused by: " Heinrich Schuchardt
2021-01-19 18:06 ` Simon Glass
2021-01-19 19:07 ` Heinrich Schuchardt
2021-01-19 19:45 ` Tom Rini
2021-01-20 0:17 ` Simon Glass
2020-11-01 21:15 ` [PATCH 07/10] setexpr: Correct dropping of final unmatched string Simon Glass
2020-12-02 21:23 ` Tom Rini
2020-11-01 21:15 ` [PATCH 08/10] setexpr: Correct buffer overflow bug and enable tests Simon Glass
2020-12-02 21:23 ` Tom Rini
2020-11-01 21:15 ` [PATCH 09/10] setexpr: Convert to use a struct for values Simon Glass
2020-12-02 21:23 ` Tom Rini
2020-11-01 21:15 ` [PATCH 10/10] setexpr: Add support for strings Simon Glass
2020-11-01 23:08 ` Marek Behun
2020-11-03 15:12 ` Simon Glass
2020-11-03 16:30 ` Marek Behun
2020-11-05 16:49 ` Wolfgang Denk
2020-11-05 17:27 ` Simon Glass
2020-11-06 20:58 ` Tom Rini [this message]
2020-11-06 21:48 ` Simon Glass
2020-11-05 16:47 ` Wolfgang Denk
2020-11-05 17:27 ` Simon Glass
2020-11-05 17:50 ` Marek Behun
2020-11-05 19:10 ` Wolfgang Denk
2020-11-05 20:15 ` Simon Glass
2020-12-02 21:23 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201106205821.GI5340@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox