Hmm. An external linting problem doesn't fit my application very well.
How do you validate field assignments in your application, Michael? I need to be able to do something like the following:
>>> a = records.ao('TEST')
>>> a.DRVL = 'wrong'
AssertionError: Can't write "test" to field DRVL: not a number
>>> a.DRVL = 123
>>> a.SCAN = 'wrong'
AssertionError: Can't write "wrong" to field SCAN: Not a valid menu choice
>>> a.SCAN = '.1 second'
>>>
From: Michael Davidsaver [mailto:[email protected]]
> If you're interested in static validation of db/dbd files, you might
> have a look at my 'dbdlint' script. This can either validate individual
> files for basic syntax (--partial), or a full database w/ recordtype
> defs (--full).
>
> This includes a handy (to me) feature to detect unintentional "external"
> links (aka typos).
>
> > $ cat test.db
> > #: external("other.VAL")
> >
> > record(longin, "target") {
> > field(INP, "other")
> > }
> >
> > record(longin, "ok") {
> > field(INP, "targt") # oops
> > }
> > $ ./dbdlint -F -Wall /path/to/base/dbd/softIoc.dbd test.db
> > WARNING test.db:8 ext-link - DB/CA Link to outside PV 'targt.VAL'
>
>
>
> https://github.com/epicsdeb/pypdb/blob/master/documentation/dbdlint.rst
> https://github.com/epicsdeb/pypdb/blob/master/dbdlint.1.txt
> https://github.com/epicsdeb/pypdb
>
>
> On 09/19/2017 01:00 PM, Andrew Johnson wrote:
> > Hi Michael,
> >
> > On 09/19/2017 04:34 AM, [email protected] wrote:
> >
> >> I have just discovered that the dbVerify function has been removed from
> >> EPICS 3.16. I use the functionality provided by this function to
> >> validate databases as they are statically constructed (in iocbuilder
> >> and epicsdbbuilder). At present DLS is still using EPICS 3.14, so I am
> >> only learning about this from external reports.
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- Replies:
- Re: dbVerify removed from EPICS 3.16 Michael Davidsaver
- References:
- dbVerify removed from EPICS 3.16 michael.abbott
- Re: dbVerify removed from EPICS 3.16 Andrew Johnson
- Re: dbVerify removed from EPICS 3.16 Michael Davidsaver
- Navigate by Date:
- Prev:
RE: dbVerify removed from EPICS 3.16 michael.abbott
- Next:
Build change from 3.14 to 3.15 michael.abbott
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: dbVerify removed from EPICS 3.16 Michael Davidsaver
- Next:
Re: dbVerify removed from EPICS 3.16 Michael Davidsaver
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|