Parse settings on the command line passed in as hex

[sbc100]

I ran into this issue when working on #15763. We have code interally
that converts =-1 to =0x7FFFFFFF for the MIN_XX_VERSION settings.
However, this was then being interpreted interally as a string. When
read from JS there is no differenence but from python code the value of
this setting would appear as the string "0x7FFFFFFF" and not the number
0x7FFFFFFF.

[kripken]

Hmm, what about cases where the user passes in 0x123 but intends that to be a string? I'm not sure I can think of an example, since it must still be a valid hex number... which means it can't be a function name or something like that.

[sbc100]

Hmm, what about cases where the user passes in 0x123 but intends that to be a string? I'm not sure I can think of an example, since it must still be a valid hex number... which means it can't be a function name or something like that.

Yes, that is right.. C/C++ symbols can't start with numbers so it can't be function name. Do you know of any other string settings that might want to be passed 0x123 as a string?

I guess the ultimate solution would be categorize the settings into those that take strings vs those that take numbers.... but that seems like a larger change.

[kripken]

I can't really think of one, so lgtm.

E.g. PTHREAD_POOL accepts a string, and in theory one could give it a hex string. But that would work with a hex number as well. I can't think of a case that can't.