Displaying 4 results from an estimated 4 matches for "allhex".
Did you mean:
alex
2020 Mar 02
2
dput()
...so new "all" is current c("all", "digits17")
> {in a way such that c("all", "hexNumeric") implicitly removes
> "digits17" (as it's in contradiction with "hexNumeric").
>
> 2) add a new option "AllHex" := c("all", "hexNumeric"),
> (Note the capital "A": such that match.arg()-like abbreviation
> of .deparseOpts() arguments remain possible and notably "all"
> does not suddenly become ambiguous)
>
> Of course, '1)'...
2020 Mar 02
0
dput()
...ot; is current c("all", "digits17")
>> {in a way such that c("all", "hexNumeric") implicitly removes
>> "digits17" (as it's in contradiction with "hexNumeric").
>>
>> 2) add a new option "AllHex" := c("all", "hexNumeric"),
>> (Note the capital "A": such that match.arg()-like abbreviation
>> of .deparseOpts() arguments remain possible and notably "all"
>> does not suddenly become ambiguous)
>>
>&g...
2020 Feb 29
2
dput()
Thanks guys, I guess I should have referred to FAQ 7.31 (which I am
indeed very familiar with) to avoid misunderstanding. I have always
used dput() to clarify 7.31-type issues.
The description in ?dput implies [to me at any rate] that there will
be no floating-point roundoff in its output. I hadn't realised that
'deparsing' as discussed in dput.Rd includes precision roundoff
issues.
2020 Mar 02
0
dput()
...e "digits17"
so new "all" is current c("all", "digits17")
{in a way such that c("all", "hexNumeric") implicitly removes
"digits17" (as it's in contradiction with "hexNumeric").
2) add a new option "AllHex" := c("all", "hexNumeric"),
(Note the capital "A": such that match.arg()-like abbreviation
of .deparseOpts() arguments remain possible and notably "all"
does not suddenly become ambiguous)
Of course, '1)' is well possible without ...