Re: Raising the 80 char limit on INP/OUT strings?

[Ralph Lange <Ralph.Lange@gmx.de>]

Michael just showed me that this limitation went away in 3.16 as part of the new link parser code.
Good!

So - what to do with 3.15?
(I'm afraid waiting for 3.16 is not short-term enough.)

I would opt for the simple version: make the buffer statically length 256.

~Ralph

On 08/04/2015 10:46, Ralph Lange wrote:

Dear all,

I have a request to raise the current limit of 80 chars on INP/OUT fields.
Some device supports (e.g. OPC, SNMP) use device-side names in that field to map signals, and names in those systems might be long.

Internally, these strings are stored in their natural length - it is just the code in dbPutString() (dbStaticLib.c 2029ff.) that sets and enforces the limit. However, having a limit makes sense to detect runaway strings (missing quotes etc.)

I see two easy feasible options:
  1. Statically raise the limit (e.g. to 256).
  2. Add an IOC variable, make the buffer static, and alloc it once (in the function).

What do you think?

Cheers,
~Ralph