![](https://secure.gravatar.com/avatar/1dea6e0a6fdffa6fd747a13f5f5e24fd.jpg?s=120&d=mm&r=g)
17 May
2010
17 May
'10
7:39 p.m.
Excellent point! As was discussed before, F=0 is most likely the consequence of a user error (improper I->F conversion protocol), F<0 clearly indicates that something is wrong and most sensible response from any program would be consider it a fatal error rather than quietly ignoring it. The information can be gleaned from the log-files, but who reads those unless something goes terribly wrong? On Mon, 2010-05-17 at 12:08 -0400, Phil Jeffrey wrote:
Again, include F=0 data. F<0 should probably immediately terminate program execution, since it infers a data content error.
-- "I'd jump in myself, if I weren't so good at whistling." Julian, King of Lemurs