pvAccess Status returns

[Ralph L. <Ral...@gm...>]

Hi,

As far as I see, we defined the Status return for a single pvAccess 
operation as a numerical severity plus string plus more data (stack 
trace etc.)

I think in this case we need a catalog of standard strings for certain 
cases (extended as more cases appear), else clients will never be able 
to properly react to certain standard status returns. (Errors like 
"insufficient privilege", "illegal value", or warnings like "numerical 
value was limited", "string was truncated" etc.)

Maybe this would be easier using an enum (maybe additional)? Usually 
APIs have enums at this point, and I am quite surprised that we have 
only a free form text. Are clients supposed to do regexp-based guessing? 
(So that they stop working in a different language environment?)

Cheers,
~Ralph