Re: dbst problem when built against 3.13.1(actually problem with capfast symbols)

[saa@SLAC.Stanford.EDU]

Hi Rozelle -

Thanks for your response on the new dbst behavior.  

>I haven't changed dbst, I simply report out fields that are different
>from the default.  It is possible that dbStaticLib has changed.  
>I believe the problem is that global link fields are  really strings, 
>so the default is the empty string rather
>than 0.00000000000e+00 (as it appears in all the capfast symbols).

Yes, dbIsDefaultValue has changed (and there is a comment in the release
notes for the changes between beta11 and beta12) so that fields with
zero's are now dumped instead of ignored.  I assume the reason for this
change is to allow people to override a field with a non-zero default value
with zero.  

>I had a problem with DOL fields inadvertantly initializing analog out
>records to 0.0.
>I went through  and did a global edit on .sym files
>that have DOL fields  and changed def(DOL) from 
>def(DOL):0.000000000000000e+00 
>to 
>def(DOL):
>This fixed our problem with analog outs.  
>However, I think this should probably be done for all the other LINK fields.
>INP, FLNK, INPA, INPB   etc.

But not just LINK fields but all non-menu fields like PHAS, EVNT, etc.
So I'll need to go through ALL my capfast symbols and edit many fields.
I wish I was using gdct as my database tool...

Thanks again,

Stephanie