Re: Arbitrary limit on timeouts?

[Eric Norum <wenorum@lbl.gov>]

Thanks for checking the provenance of this.

I can see the usefulness of the sanity check limit to non-negative timeouts but the arbitrary upper limit seems like a bad idea. Maybe it’s too late to change now — there may be some existing code that depends on this.   At the very least the behaviour should be noted in the application developers guide.  

On Jun 7, 2017, at 10:38 AM, Michael Davidsaver <mdavidsaver@gmail.com> wrote:

On 06/07/2017 06:50 PM, Eric Norum wrote:

Why are timeouts for things like epicsEventWaitWithTImeout() limited to
1 hour?
This is for R3.15.4, but I suspect the code is the same in lots of versions.

Since at least 2000 (first occurrence I find).  The commit message
doesn't give any clues.

https://github.com/epics-base/epics-base/commit/8c60195f4b463bff42f6f967da8bc19d6f5ad11d#diff-583652b37e7f98cf7b720e489744ce88R57

Seems rather arbitrary, so I think this could be removed (or enlarged).