Re: HEADSUP: i2c(8) has been washed and ironed
jake h writes: > > What about adding a new flag to enable strtoul behavior? > I have had a look at the available flag options for a potential strtoul > flag, and a flag that makes sense to me is [-s] / [--strtoul]. [-s] is not > currently being used in i2c, if we wanted to use it. -s is already used to select "scan" mode. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HEADSUP: i2c(8) has been washed and ironed
> What about adding a new flag to enable strtoul behavior? I have had a look at the available flag options for a potential strtoul flag, and a flag that makes sense to me is [-s] / [--strtoul]. [-s] is not currently being used in i2c, if we wanted to use it. On Fri, May 14, 2021 at 5:13 AM Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: > > I have renovated the i2c(8) program and while I belive all argument > > processing is 100% compatible, various undocumented aspects of the > > program may have changed, amongst these precisely what goes to > > stdout and stderr. > > > > Apologies if this breaks any of your scripts. > > > > > > > > There is one aspect of this program which I have not changed, but > > which bugs me utterly: All arguments are in hex, except [-c count] > > which is decimal. > > > > My personal preference would be if all the arguments called strtoul(3) > > with zero third argument, so that users can use decimal, octal or > > hex as they prefer, but I fear that would break pretty much every > > single script. > > > > Alternatively [-c count] could be changed to be hex like the rest. > > What about adding a new flag to enable strtoul behavior? > Or invoked by another name i2cX and install a hard link? > > > > > > > p...@freebsd.org | TCP/IP since RFC 956 > -- > Rod Grimes > rgri...@freebsd.org > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HEADSUP: i2c(8) has been washed and ironed
> I have renovated the i2c(8) program and while I belive all argument > processing is 100% compatible, various undocumented aspects of the > program may have changed, amongst these precisely what goes to > stdout and stderr. > > Apologies if this breaks any of your scripts. > > > There is one aspect of this program which I have not changed, but > which bugs me utterly: All arguments are in hex, except [-c count] > which is decimal. > > My personal preference would be if all the arguments called strtoul(3) > with zero third argument, so that users can use decimal, octal or > hex as they prefer, but I fear that would break pretty much every > single script. > > Alternatively [-c count] could be changed to be hex like the rest. What about adding a new flag to enable strtoul behavior? Or invoked by another name i2cX and install a hard link? > > p...@freebsd.org | TCP/IP since RFC 956 -- Rod Grimes rgri...@freebsd.org ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
HEADSUP: i2c(8) has been washed and ironed
I have renovated the i2c(8) program and while I belive all argument processing is 100% compatible, various undocumented aspects of the program may have changed, amongst these precisely what goes to stdout and stderr. Apologies if this breaks any of your scripts. There is one aspect of this program which I have not changed, but which bugs me utterly: All arguments are in hex, except [-c count] which is decimal. My personal preference would be if all the arguments called strtoul(3) with zero third argument, so that users can use decimal, octal or hex as they prefer, but I fear that would break pretty much every single script. Alternatively [-c count] could be changed to be hex like the rest. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
