Hi Ben,
Thanks for the Good work,
though perl is even harder to read than ed scripts, so at the
moment I am trusting that this does what you say it does.
I think it would be a really bad idea to edit existing schematics. Default
values don't appear in schematics, only values that overwrite defaults
actually show up in the .sch files.
Rozelle
> From [email protected] Wed Mar 3 11:03 MST 1999
> Sender: [email protected]
> Date: Wed, 03 Mar 1999 19:03:01 +0100
> Organization: BESSY
> X-Mailer: Mozilla 3.0 (X11; I; HP-UX B.10.20 9000/782)
> MIME-Version: 1.0
> To: Rozelle Wright <[email protected]>
> CC: EPICS Techtalk <[email protected]>
> Subject: Re: dbst problem when built against 3.13.1(actually problem with capfast symbols)
> References: <[email protected]> <[email protected]>
> Content-Transfer-Encoding: 7bit
> X-Lines: 38
>
> Hi Rozelle,
>
> > > Hi Ben,
> > > Did you ever write that Perl script?
> >
> > Unfortunately not! I could not decide to make the changes in our
> > edif-sym directory because I feared that older applications (using older
> > epics releases) might break. [...]
>
> My fears were not justified. I didn't realize that dbst is an epics
> _extension_ and therefore has only one instance at our site and not one
> for every base release, like eg dbLoadRecords. So we have been using the
> new dbst all along.
>
> Anyway, we are currently trying to adjust our site to the new
> source/release control. Thus we treat the directory for capfast symbols
> and edb.def like a <supporttop> so the cleansed direcory is used only
> for 3.13.1 applications. This is my 'script':
>
> perl -pi -e 's/:0(\.0+(e\+0+)?)?$/:/g' *.sym
> perl -pi -e 's/\(default\("0?(\.0+(e\+0+)?)?"\)\)//g' edb.def
> perl -pi -e 's/\(default\s+"0?(\.0+(e\+0+)?)?"\)//g' edb.def
>
> It eliminates all zero values in the symbols, as well as all zero value
> and empty string defaults in the edb.def (no backup). Do existing
> schematics need be cleansed of zeros? In any case, I wouldn't do it
> automatically because there may be zeros that are meant to be in there
> to override other defaults. I don't think we need to edit any capfast
> symbol or edb.def manually.
>
> Ben
> --
> The Notorious Neb Nesknarf
> ---------------------------------------------------------------------
> @BESSY II: fax: +49 30 6392-4859 phone: +49 30 6392-4865
> ---------------------------------------------------------------------
> keep the listeners happy: BND MAD Waffen Lieferung ETA Lybien IRA CIA
> Iran killer Heroin kommunistische Befreiungsfront RAF PKK Irak Kurden
>
- Replies:
- Re: dbst problem when built against 3.13.1(actually problem with capfast symbols) Ralph Lange
- Navigate by Date:
- Prev:
Re: dbst problem when built against 3.13.1(actually problem with capfast symbols) Benjamin Franksen
- Next:
Job Opportunities Hamid Shoaee
- 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: dbst problem when built against 3.13.1(actually problem with capfast symbols) Benjamin Franksen
- Next:
Re: dbst problem when built against 3.13.1(actually problem with capfast symbols) Ralph Lange
- 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
|