Re: RFC: "set" command with 2 arguments instead of one?

Andreas Schwab
2014-11-23T09:32:50Z

Joel Brobecker <brobecker@adacore.com> writes:

> It proposes the introduction of a couple of commands, one to dump
> the contents of the of the bounds table, and one to set the bounds
> for any given address. Since those commands are MPX-specific,
> I would like to have them prefixed somehow. But the beyond the
> fact that I'd like to have them prefixed, I was wondering if
> set/show commands could be used for that. Eg:
>
> show mpx bound ADDR
> set mpx bound ADDR LBOUND UBOUND
>
> The reason why I am asking for comments is that the "set" command
> above has a syntax which is slightly unusual for "set" commands
> in the sense that "set" commands nearly always only have one argument,
> whereas it has 3 in this case.

How do you parse the arguments if they are arbitrary expressions?

Andreas.

--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."