Access security expressions use TRUE=1, FALSE=anything else
Bug #541390 reported by
Andrew Johnson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| EPICS Base |
Won't Fix
|
Wishlist
|
mdavidsaver | ||
Bug Description
Can't change this in R3.14 since it would break too much, but a CALC expression should be able to return a regular TRUE/FALSE value.
Additional information:
See Marty Smith's tech-talk email of 2009-09-10 07:02
Original Mantis Bug: mantis-367
http://
Revision history for this message
| mdavidsaver (mdavidsaver) wrote | #1 |
| Changed in epics-base: | |
| assignee: | nobody → mdavidsaver (mdavidsaver) |
| status: | New → Won't Fix |
To post a comment you must log in.
While confusing, this behavior is documented in asLib.h and the appdev guide, I don't see any benefit to breaking this API.