10 Bucks to see ...

Originally Posted by
ErnieM
Go ahead and bet your dollar. I'm using PBP for software in a human patient connected device. If my device fails to work when it's supposed to that person will die.
You can bet your buck but I'm not betting someone's life on an undocumented "feature."
I do code very defensively when using integer math; typically checking inputs for values in the expected range to keep the output from overflowing is sufficient.
Hi, Ernie
Great to you, but, as the source code is available ( PbP**.lib ), you can verify it quietly. Add to that it can easily be verified " live ( ! ) " in a little test example, using MPLAB in debugging mode ...
One more thing ... I remember having read somewhere those softs do not guarantee they are bug free ( special lines for life critical systems , last page of the manual ... also saw that lines from µChip datas !!! ).
Sooo , documented or not, it's all at your own risks ... and you have to verify everything.
Just for fun ... most of my systems are intended to care of the flying security of giant size model aircrafts ...
We're aboard the same boat, it seems ...
Regards
Alain
Last edited by Acetronics2; - 13th October 2006 at 19:59.
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Bookmarks