epicsMessageQueue
-The epicsMessageQueue API has been changed. All functions and methods -to receive a message now have an additional argument which specifies the size -of the receiver buffer. The receive functions/methods return -1 and the + +
The epicsMessageQueue API has been changed. All functions and methods to +receive a message now have an additional argument which specifies the size of +the receiver buffer. The receive functions/methods return -1 and the received message is discarded if the received message will not fit in the -buffer. -See the Application Developer's Guide (libCom OSI) for details.
--This is an incompatible change. All R3.14.2 applications which use -epicsMessageQueue must be modified before they can be compiled and -used with R3.14.3
+buffer. See the Application Developer's Guide (libCom OSI) for details. + +This is an incompatible change. All R3.14.2 applications which use +epicsMessageQueue must be modified before they can be compiled and used with +R3.14.3
+ +A bug occurring only in Microsoft Windows port of the error message +logging client was fixed. The symptoms were problems getting a Microsoft +Windows based IOC to make entries in the log file.
+ +A bug occurring in the error message logging server where a partial +message arrives w/o a <CR> and then a <CR> from a previous +message was found in the input buffer was fixed. The problem must have +existed for a long time but probably was not occurring frequently. The +symptom was garbled output in the log file.
Build System
-Major changes have been made to the build system. -The good news is that the rules for support and ioc applications -are now greatly simplified. The bad news is that it does mean -changes for existing 3.14.1 applications. Please see:
-ConvertingR3.14.1AppsToR3.14.2
-for details. If you are using the function DBD keyword it no -longer exists. Please read this conversion document for details.
+ +Major changes have been made to the build system. The good news is that +the rules for support and ioc applications are now greatly simplified. The +bad news is that it does mean changes for existing 3.14.1 applications. +Please see:
+ +ConvertingR3.14.1AppsToR3.14.2
+ +for details. If you are using the function DBD keyword it +no longer exists. Please read this conversion document for details.
Application Developer's Guide
-The old chapter "New Feature's for 3.14" has been replaced by -a new chapter "Getting Started". Please read it. It provides -a simplified set of rules that can be used to build most -support and ioc applications. Many minor changes have also been made.
+ +The old chapter "New Feature's for 3.14" has been replaced by a new +chapter "Getting Started". Please read it. It provides a simplified set of +rules that can be used to build most support and ioc applications. Many minor +changes have also been made.
dbGetLink
-A bug in dbGetLink resulted in nRequest not being given the value 0 -if the link is a constant link. This in turn caused the waveform -record to always set NORD=NELEM. Thus if an application trys -to write a waveform via the steps:
-- prset->get_array_info(paddr,&no_elements,&offset); - << write nNew elements into array >> - prset->put_array_info(paddr,nNew); --
This sets NORD = nNew. -But because of the dbGetLink bug, the soft device support attached to -the waveform record sets NORD to NELM.
+ +A bug in dbGetLink resulted in nRequest not being given the value 0 if the +link is a constant link. This in turn caused the waveform record to always +set NORD=NELEM. Thus if an application trys to write a waveform via the +steps:
+prset->get_array_info(paddr,&no_elements,&offset); + write nNew elements into array >> + prset->put_array_info(paddr,nNew);+ +
This sets NORD = nNew. But because of the dbGetLink bug, the soft device +support attached to the waveform record sets NORD to NELM.
+This problem is fixed. The actual bug was in macros in dbAccessDefs.h
Access Security
-The host names are now converted to lower case. -This fixes incompatibilities between various platforms.
+ +The host names are now converted to lower case. This fixes +incompatibilities between various platforms.
string records
-Both the stringin and stringout records have two new DBF_MENU fields: -APST and MPST. These control whether CA monitors are fired if the new VAL -field string is identical to the old one. The default (zero) menu value is -"On Change" with behaviour identical to before, -set to "Always" if you want a record to fire monitors every time the record -is processed (analagous to setting ADEL/MDEL=-1 for numeric record types).
+ +Both the stringin and stringout records have two new DBF_MENU fields: APST +and MPST. These control whether CA monitors are fired if the new VAL field +string is identical to the old one. The default (zero) menu value is "On +Change" with behaviour identical to before, set to "Always" if you want a +record to fire monitors every time the record is processed (analagous to +setting ADEL/MDEL=-1 for numeric record types).
epicsMessageQueue
-A new facility that provides the capabilities of vxWorks msgQLib. -See the Application Developer's Guide (libCom OSI) for details.
+ +A new facility that provides the capabilities of vxWorks msgQLib. See the +Application Developer's Guide (libCom OSI) for details.
epicsStdio and errlogPrintf
-A new facility has been added to libCom described by epicsStdio.h. -It contains the functions epicsSnprintf and epicsVsnprintf. -These are like the C99 functions snprintf and vsnprintf, -which are like sprintf and vsprintf except that they accept a argument -limiting the number of characters written.
-The errlogPrintf facility has been modified to use this facility. -Thus it is not longer subject to a possible buffer overflow.
+ +A new facility has been added to libCom described by epicsStdio.h. It +contains the functions epicsSnprintf and epicsVsnprintf. These are like the +C99 functions snprintf and vsnprintf, which are like sprintf and vsprintf +except that they accept a argument limiting the number of characters +written.
+ +The errlogPrintf facility has been modified to use this facility. Thus it +is not longer subject to a possible buffer overflow.
scanPeriod
-This is a new function provided by the Database Scanning facility. -Given an index for the choices defined by menuScan.h, it returns -the scan period in seconds. The argument can just be the scan field -of a database record. If the index is not associated with a periodic -scan rate, the value 0.0 is returned.
+ +This is a new function provided by the Database Scanning facility. Given +an index for the choices defined by menuScan.h, it returns the scan period in +seconds. The argument can just be the scan field of a database record. If the +index is not associated with a periodic scan rate, the value 0.0 is +returned.
New epicsString.h function
-A new function epicsStrCaseCmp has been added. It is like strcmp -except that it ignores case.
+ +A new function epicsStrCaseCmp has been added. It is like strcmp except +that it ignores case.
macLib
-macParseDefns did not check for handle==NULL. -The documentation for macParseDefns was not correct.
+ +macParseDefns did not check for handle==NULL. The documentation for +macParseDefns was not correct.