From fe1ec6ed3132c40d4a4e2dbe7bcfff0ca234572c Mon Sep 17 00:00:00 2001
From: Andrew Johnson
- if (prec->siml.type == CONSTANT) {
- recGblInitConstantLink(&prec->siml, DBF_USHORT, &prec->simm);
+ if (prec->siml.type == CONSTANT) {
+ recGblInitConstantLink(&prec->siml, DBF_USHORT, &prec->simm);
}
into this:
- recGblInitConstantLink(&prec->siml, DBF_USHORT, &prec->simm); + recGblInitConstantLink(&prec->siml, DBF_USHORT, &prec->simm);Note that recGblInitConstantLink() still returns TRUE if the field was @@ -328,20 +328,20 @@ or undefined links, FALSE for links whose dbGetLink() routine may return different values on different calls. For example this:
- if (prec->dol.type != CONSTANT) + if (prec->dol.type != CONSTANT)should become this:
- if (!dbLinkIsConstant(&prec->dol)) + if (!dbLinkIsConstant(&prec->dol))When the converted software is also required to build against older versions of Base, this macro definition may be useful:
-#define dbLinkIsConstant(lnk) ((lnk)->type == CONSTANT) +#define dbLinkIsConstant(lnk) ((lnk)->type == CONSTANT)@@ -349,7 +349,7 @@ Base, this macro definition may be useful: link has been resolved as a CA link using code such as
- if (prec->inp.type == CA_LINK) + if (prec->inp.type == CA_LINK)will still compile and run, but will only work properly with the old CA link @@ -359,7 +359,7 @@ examine or modify data inside the link. After conversion the above line would probably become:
- if (dbLinkIsVolatile(&prec->inp)) + if (dbLinkIsVolatile(&prec->inp))A volatile link is one like a Channel Access link which may disconnect and @@ -369,7 +369,7 @@ same state they started in. For compatibility when building against older versions of Base, this macro definition may be useful:
-#define dbLinkIsVolatile(lnk) ((lnk)->type == CA_LINK) +#define dbLinkIsVolatile(lnk) ((lnk)->type == CA_LINK)