R4.1 is breaking backward compatibility

[ralphlange]

Commit 37baacc added a third argument to the initialization call that is part of the public API.
That change is not compatible: IOCs that work fine with R4.0 fail to start using R4.1.

Please add a compatibility init function (using the old argument list) that calls the new init function with a reasonable third argument. Printing a deprecation warning on the iocShell console would also be fine.

IMHO, API-breaking changes need to be well-documented and should be avoided for minor version jumps.

[anjohnson]

I guess we assumed that initialization would be done in an st.cmd file, where the final argument gets a default value of 0 if not provided. The code checks for that and uses the original value of DEFAULT_BURST_TIMEOUT seconds instead.

For my edification, how are you initializing this if not from an iocsh command?

[ralphlange]

The CA Gateway does not have a st.cmd file...

(I know, I wrote "IOCs", which is obviously wrong and related to sleep deprivation.)

[anjohnson]

Ack, my apologies. I remember now that we don't build the Gateway with CAPUTLOG here because it doesn't generate the JSON put-logging format that we wanted. The -putlog <file> option still generates a local putlog file, although that doesn't contain the values being written.

[ralphlange]

A macro would probably be good enough.
Either a macro with the old call spec or some feature-existence macro that the Gateway can use to work with both <=4.0 and >=4.1