Yosef Meller
2005-02-26 08:38:46 UTC
Attached are the help files for sk6100. I hope I got it right.
Also attached is a diff to fix an ommition of a phone type category that
caused an exception when that category was used for an entry.
I thought about checking if the phone type id is out of range and
falling back to some default, which would be useful for supporting more
advanced models with the same code, and it would also be harder to make
it fail for a user.
On the other hand, maybe it *should* crash on data I didn't prepare for,
so it wouldn't leave the factory gates damaged. Also, I think that the
spirit here is that new models get new implementations or nothing,
leaving the guesswork and the 'maybe it just works' out of the project.
Looks to me like my first thoughts are the 'perl way' vs the 'python way'.
So, which one? What do you think?
Also attached is a diff to fix an ommition of a phone type category that
caused an exception when that category was used for an entry.
I thought about checking if the phone type id is out of range and
falling back to some default, which would be useful for supporting more
advanced models with the same code, and it would also be harder to make
it fail for a user.
On the other hand, maybe it *should* crash on data I didn't prepare for,
so it wouldn't leave the factory gates damaged. Also, I think that the
spirit here is that new models get new implementations or nothing,
leaving the guesswork and the 'maybe it just works' out of the project.
Looks to me like my first thoughts are the 'perl way' vs the 'python way'.
So, which one? What do you think?
--
"Necessity may be the mother of invention but coffee is the fuel."
- seen on web.archive.org
"Necessity may be the mother of invention but coffee is the fuel."
- seen on web.archive.org