Fix spelling errors

Most errors found with:

codespell -L cach,thst,odly,aslo,parm,parms,inpu,ges,prset,pevent,ptd,pring,valu,noo,noe,ned,inout,ro,siz,froms,nd,fo,singl,sart,multy,tthe,allong,ment,inate,nodel,tring,alse,ture,thi,wille,numer

Some more manually found (its -> it's)

c++20: Do not use apostrophe (e.g. can't) in unquoted #error message
This commit is contained in:
2025-11-25 13:51:56 +01:00
committed by mdavidsaver
parent 4f547230c4
commit 90a727c901
159 changed files with 275 additions and 275 deletions
+1 -1
View File
@@ -40,7 +40,7 @@ link(const, lnkConstIf)
=head3 Constant Link C<"const">
Constant links are input links that provide literal values at link initalization
Constant links are input links that provide literal values at link initialization
time, but do not return any data when their C<getValue()> routine is called.
Most record types support the use of constant links on their input links by
calling C<recGblInitConstantLink()> at record initialization, which results in
@@ -338,7 +338,7 @@ during record processing.
=head3 Input Value Fields
Thse fields hold the scalar or array values fetched through the input links
These fields hold the scalar or array values fetched through the input links
INPA,...,INPU.
=fields A - U
+1 -1
View File
@@ -113,7 +113,7 @@ static long init_record(struct dbCommon *pcommon, int pass)
return(S_dev_missingSup);
}
prec->init = TRUE;
/*The following is for old device support that doesnt know about eoff*/
/*The following is for old device support that doesn't know about eoff*/
if ((prec->eslo==1.0) && (prec->eoff==0.0)) {
prec->eoff = prec->egul;
}
+1 -1
View File
@@ -118,7 +118,7 @@ static long init_record(struct dbCommon *pcommon, int pass)
return(S_dev_missingSup);
}
prec->init = TRUE;
/*The following is for old device support that doesnt know about eoff*/
/*The following is for old device support that doesn't know about eoff*/
if ((prec->eslo==1.0) && (prec->eoff==0.0)) {
prec->eoff = prec->egul;
}
@@ -224,8 +224,8 @@ alarms that are common to all record types.
These parameters are used to specify deadbands for monitors on the VAL
field. The monitors are sent when the value field exceeds the last
monitored field by the specified deadband. If these fields have a value
of zero, everytime the value changes, a monitor will be triggered; if
they have a value of -1, everytime the record is processed, monitors
of zero, every time the value changes, a monitor will be triggered; if
they have a value of -1, every time the record is processed, monitors
are triggered. ADEL is the deadband for archive monitors, and MDEL the
deadband for all other types of monitors. See Monitor Specification for
a complete explanation of monitors.
@@ -99,7 +99,7 @@ These parameters are used to determine if the binary input is in alarm
condition and to determine the severity of that condition. The possible
alarm conditions for binary inputs are the SCAN, READ state alarms, and the
change of state alarm. The SCAN and READ alarms are called by the device
supprt routines.
support routines.
The user can choose the severity of each state in the ZSV and OSV fields.
The possible values for these fields are C<NO_ALARM>, C<MINOR>, and
@@ -126,7 +126,7 @@ MASK is given a value by ithe device support routines. This value is used to
manipulate the record's value, but is only the concern of the hardware device
support routines.
The LALM fields holds the value of the last occurence of the change of
The LALM fields holds the value of the last occurrence of the change of
state alarm. It is used to implement the change of state alarm, and thus
only has meaning if COSV is MAJOR or MINOR.
@@ -407,7 +407,7 @@ Scan forward link if necessary, set PACT FALSE, and return.
=head3 Fields of Interest to Device Support
Each binary input record must have an associated set of device support
routines. The primary resposibility of the device support routines is to
routines. The primary responsibility of the device support routines is to
obtain a new raw input value whenever C<read_bi()> is called. The device
support routines are primarily interested in the following fields:
@@ -391,7 +391,7 @@ If either device support or the device support write routine does not
exist, and error message is issued and processing is terminated.
If DOL is a constant, then VAL is initialized to 1 if its value is nonzero
or initialzed to 0 if DOL is zero, and UDF is set to FALSE.
or initialized to 0 if DOL is zero, and UDF is set to FALSE.
If device support includes C<init_record()>, it is called. VAL is set using
RVAL, and UDF is set to FALSE.
@@ -442,7 +442,7 @@ Result is C<E> if C<<< (A + B)<(C + D) >>>
=item *
Result is unchanged if C<<< (A + B)>=(C + D) >>>
From 3.14.9 onwards, this expresion must be written as
From 3.14.9 onwards, this expression must be written as
C<<< (A + B) < (C + D) ? E : VAL >>>
=back
@@ -537,8 +537,8 @@ These paramaeters are used to determine when to send monitors for the value
fields. These monitors are sent when the value field exceeds the last
monitored field by the appropriate deadband, the ADEL for archiver monitors
and the MDEL field for all other types of monitors. If these fields have a
value of zero, everytime the value changes, monitors are triggered; if they have a
value of -1, everytime the record is scanned, monitors are triggered. See
value of zero, every time the value changes, monitors are triggered; if they have a
value of -1, every time the record is scanned, monitors are triggered. See
L<Monitor Specification> for a complete explanation of monitors.
=fields ADEL, MDEL
@@ -121,7 +121,7 @@ holds the average of the first element of INP over N samples, VAL[1] holds the
average of the next element of INP over N samples, and so on. The following
shows the equation:
=for comment Latex form of equation bellow : VAL[i] \leftarrow \frac{1}{N}\sum_{n=1}^NINP_{n}[i]
=for comment Latex form of equation below : VAL[i] \leftarrow \frac{1}{N}\sum_{n=1}^NINP_{n}[i]
=begin html
@@ -42,7 +42,7 @@ These fields are listed in L<Scan Fields|dbCommonRecord/Scan Fields>.
=head3 Desired Output Parameters
The data fanout record must specify where the desired output value
originates, i.e., the data which is to be fowarded to the records in its
originates, i.e., the data which is to be forwarded to the records in its
output links. The output mode select (OMSL) field determines whether the
output originates from another record or from run-time database access.
When set to C<closed_loop>, the desired output is retrieved from the link
@@ -156,8 +156,8 @@ These parameters are used to determine when to send monitors placed on the
VAL field. These monitors are sent when the value field exceeds the last
monitored fields by the specified deadband, ADEL for archivers monitors and
MDEL for all other types of monitors. If these fields have a value of zero,
everytime the value changes, a monitor will be triggered; if they have a
value of -1, everytime the record is scanned, monitors are triggered. See
every time the value changes, a monitor will be triggered; if they have a
value of -1, every time the record is scanned, monitors are triggered. See
L<Monitor Specification> for a complete explanation of monitors.
=fields ADEL, MDEL
@@ -165,7 +165,7 @@ L<Monitor Specification> for a complete explanation of monitors.
=head3 Run-Time Parameters and Simulation Mode Parameters
These parameters are used by the run-time code for processing the data
fanout record. Ther are not configurable. They are used to implement the
fanout record. They are not configurable. They are used to implement the
hysteresis factors for monitor callbacks.
=fields LALM, ALST, MLST
@@ -70,7 +70,7 @@ alarms that are common to all record types.
The MDEL field implements the monitor count deadband. Only when MCNT is greater
than the value given to MDEL are monitors triggered, MCNT being the number of
counts since the last time the record was processed. If MDEL is -1, everytime
counts since the last time the record was processed. If MDEL is -1, every time
the record is processed, a monitor is triggered regardless.
If SDEL is greater than 0, it causes a callback routine to be called. The number
@@ -93,8 +93,8 @@ alarms that are common to all record types.
These parameters are used to determine when to send monitors placed on the value
field. The monitors are sent when the value field exceeds the last monitored
field (see the next section) by the appropriate deadband. If these fields have a
value of zero, everytime the value changes, a monitor will be triggered; if they
have a value of -1, everytime the record is scanned, monitors are triggered. The
value of zero, every time the value changes, a monitor will be triggered; if they
have a value of -1, every time the record is scanned, monitors are triggered. The
ADEL field is used by archive monitors and the MDEL field for all other types of
monitors.
@@ -312,9 +312,9 @@ to alarms that are common to all record types.
These parameters are used to determine when to send monitors placed on the value
field. The monitors are sent when the value field exceeds the last monitored
field by the appropriate delta. If these fields have a value of zero, everytime
field by the appropriate delta. If these fields have a value of zero, every time
the value changes, a monitor will be triggered; if they have a value of -1,
everytime the record is scanned, monitors are triggered. The ADEL field is the
every time the record is scanned, monitors are triggered. The ADEL field is the
delta for archive monitors, and the MDEL field is the delta for all other types
of monitors. See L<Monitor Specification> for a complete explanation of
monitors.
@@ -16,7 +16,7 @@ It can accept boolean values in its 32 bit fields (B0-B9, BA-BF, B10-B19 and
B1A-B1F), and converts them to a 32-bit signed integer in VAL which is provided
to the device support. A zero value in a bit field becomes a zero bit in VAL, a
non-zero value in a bit field becomes a one bit in VAL, with B0 being the least
signficant bit and B1F the MSB/sign bit.
significant bit and B1F the MSB/sign bit.
=recordtype mbboDirect
@@ -47,7 +47,7 @@ placed into the VAL field.
When OMSL is set to C<<< supervisory >>>, the DOL field is ignored during
processing and the contents of VAL are used. A value to be output may thus be
written direcly into the VAL field from elsewhere as long as the record is in
written directly into the VAL field from elsewhere as long as the record is in
C<<< supervisory >>> mode.
=fields OMSL, DOL, VAL
@@ -36,7 +36,7 @@ These fields are described in L<Scan Fields|dbCommonRecord/Scan Fields>.
The printf record must specify the desired output string with embedded format
specifiers in the FMT field. Plain characters are copied directly to the output
string. A pair of percent characters 'C<%%>' are converted into a single percent
character in the output string. A single precent character 'C<%>' introduces a
character in the output string. A single percent character 'C<%>' introduces a
format specifier and is followed by zero or more of the standard C<printf()>
format flags and modifiers:
@@ -133,8 +133,8 @@ alarms that are common to all record types.
These fields are configurable by the user. They are used as deadbands for the
archiver and monitor calls for the VAL field. Unless, VAL changes by more than
the value specified by each, then the respective monitors will not be called. If
these fields have a value of zero, everytime the VAL changes, monitors are
triggered; if they have a value of -1, everytime the record is processed,
these fields have a value of zero, every time the VAL changes, monitors are
triggered; if they have a value of -1, every time the record is processed,
monitors are triggered.
=fields ADEL, MDEL
@@ -100,8 +100,8 @@ field. The appropriate monitors are invoked when VAL differs from the values in
the ALST and MLST run-time fields, i.e., when the value of VAL changes by more
than the deadband specified in these fields. The ADEL and MDEL fields specify a
minimum delta which the change must surpass before the value-change monitors are
invoked. If these fields have a value of zero, everytime the value changes, a
monitor will be triggered; if they have a value of -1, everytime the record is
invoked. If these fields have a value of zero, every time the value changes, a
monitor will be triggered; if they have a value of -1, every time the record is
processed, monitors are triggered. The ADEL field is used by archive monitors
and the MDEL field for all other types of monitors.
@@ -290,7 +290,7 @@ This example for a VxWorks IOC shows an asynchronous subroutine. It uses
(actually misuses) fields A and B. Field A is taken as the number of seconds
until asynchronous completion. Field B is a flag to decide if messages should be
printed. Lets assume A E<gt> 0 and B = 1. The following sequence of actions will
occcur:
occur:
=over
+1 -1
View File
@@ -4,7 +4,7 @@
# Fixed menus
include "menuGlobal.dbd"
# Modifyable menus
# Modifiable menus
include "menuConvert.dbd"
include "menuScan.dbd"
@@ -72,7 +72,7 @@ void usage(const char *arg0, const std::string& base_dbd) {
" -D <dbd> If used, must come first. Specify the path to the softIoc.dbdfile."
" The compile-time install location is saved in the binary as a default.\n"
"\n"
" -h Print this mesage and exit.\n"
" -h Print this message and exit.\n"
"\n"
" -S Prevents an interactive shell being started.\n"
"\n"