| Subject: | Weather:Com dies on error rather than throwing a recoverable error |
When errors are encountered (such as a bad location or bad key), the
routine 'dies' rather than throwing a recoverable error.
I want to call the weather routines as part of a larger program and I
don't want the program itself to die just because there is a problem
with the weather.com inputs.
It would be better if instead a 'warn' level error were issued along
with an error return code. Then each programmer can decide what to do
when such an error is encountered (including whether they want to die
or recover from the error).
I can't see any benefit of having a blanket die response.
My particular concern is that I wouldn't want my broader program which
runs as a daemon to suddenly die one day just because my license
expired.
Thanks