EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  <19961997  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  Index 1994  1995  <19961997  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 
<== Date ==> <== Thread ==>

Subject: RE: e2sr and the CALC record
From: "Eric Bjorklund, NPSM" <[email protected]>
To: [email protected]
Date: Mon, 1 Apr 1996 11:37:53 -0700 (MST)
> Matthew(s),
>
> I have just started using version 2.1.3 of 'e2sr' in order to
> make use of the macro substitution through a heirarchy of schematics.
> However, I seem to have found a bug with the CALC field of calculation records.
>
> If you set the CALC field as: A%6
> (which I believe is allowable, as stated in the record reference manual).
> The result in the '.sr' file is: A%67 !!
> 
> I went through the following to generate this:
> 
> sch2edif -n test.sch.  (Version 2.2.74)
> 
> (Incidently, this gave me a file which had the following:
> 
>               (property (rename def "def")
>                 (string "test:calc1.B"))))
>           (instance (rename calc1 "calc1")
>             (viewRef NETLIST_VIEW 
>               (cellRef ecalcs))
>             (property (rename CALC "CALC")
>               (string "A%37%6")))
>           (net (rename n_22 "n#22")
>  
> Where does the extra "%37" come from?) 
> 

Andy,

I have run into the same problem.  edif uses the % as an escape character, so
%37% is an "escaped %" (37 is decimal for the percent character). 
The bug is in the file edifRead.c, which doesn't correctly keep track of the
end-of-string after parsing an escape sequence (this results in the A%67 you
observed).

I have been working on this and various other problems with e2sr (mostly having
to do with using busses) and have a fix which I can put into our anonymous ftp
site (once I figure out where it is and how to do it) or mail to you directly,
whichever you prefer.

I have not observed the problems with B=0?1:A or B*(A+1) that you mention, but
I don't use CAPFAST 3.02 either.  It might be interesting to see what the .edf
file looks like for these records.

						Eric Bjorklund
						AOT-6  LANSCE Operations
						[email protected]



Navigate by Date:
Prev: Capfast 3.02.23 and CALC records Andy Foster
Next: Re: Capfast 3.02.23 and CALC records Nick Rees
Index: 1994  1995  <19961997  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: e2sr and the CALC record Andy Foster
Next: Capfast 3.02.23 and CALC records Andy Foster
Index: 1994  1995  <19961997  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·