2006/1/27, Peter Selinger <selinger@mathstat.dal.ca>:> > ... > battery.mfr.date, which is probably the more accurate interpretation. > >I think the naming should be changed to propose both: - battery.date.mfr: Battery manufacturing date - battery.date.change: Battery change date Any comments? Arnaud -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20060127/942505e3/attachment.html
I simply used the existing variable name from docs/new-names.txt: |-------------------------+------------------------------+---------------| | battery.mfr.date | Battery manufacturing date | 2005/04/02 | | | (opaque string) | | |-------------------------+------------------------------+---------------| Perhaps it makes sense to change it, but then probably in all drivers at the same time. -- Peter Arnaud Quette wrote:> > 2006/1/27, Peter Selinger <selinger@mathstat.dal.ca>: > > > > ... > > battery.mfr.date, which is probably the more accurate interpretation. > > > > > I think the naming should be changed to propose both: > - battery.date.mfr: Battery manufacturing date > - battery.date.change: Battery change date > > Any comments? > > Arnaud
On Fri, 27 Jan 2006, Arnaud Quette wrote:> I think the naming should be changed to propose both: > - battery.date.mfr: Battery manufacturing date > - battery.date.change: Battery change date > > Any comments?Seems reasonable. Or simply battery.mfr and battery.change to get a common naming. I'd prefer that to renaming the other variables to things like battery.ampere.charge and battery.seconds.runtime ... /Nikke -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke@acc.umu.se --------------------------------------------------------------------------- Captain, a Klingon does NOT play Tetris. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=