Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  Index 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022 
<== Date ==> <== Thread ==>

Subject: RE: EPICS base V4: iocCore database
From: Jeff Hill <johill@lanl.gov>
To: 'Benjamin Franksen' <benjamin.franksen@bessy.de>
Cc: 'Marty Kraimer' <mrk@aps.anl.gov>, 'Andrew Johnson' <anj@aps.anl.gov>, 'Bob Dalesio' <ldalesio@lanl.gov>, 'Ralph Lange' <Ralph.Lange@mail.bessy.de>, 'Eric Norum' <norume@aps.anl.gov>, 'Ken Evans' <evans@aps.anl.gov>, 'Ned Arnold' <nda@aps.anl.gov>, 'Matej Sekoranja' <matej.sekoranja@ijs.si>
Date: Wed, 23 Feb 2005 10:40:01 -0700
> I was only talking about record field and corresponding 
> CA data types.

A common design goal is to not allow the details of internal data
structures to be exposed by externally visible interfaces. Among
other benefits, this prevents changes in the internal
implementation from impacting clients of the interface (sorry to
restate motherhood and apple pie). However, with a large
distributed system such as EPICS it is quite convenient at times
to peek under the hood at the data structures of the internal
implementation using channel access for debugging purposes.
Therefore, from my perspective, support for unsigned types used
in the internal implementation can also be of value.

Jeff

> -----Original Message-----
> From: Benjamin Franksen [mailto:benjamin.franksen@bessy.de]
> Sent: Wednesday, February 23, 2005 9:10 AM
> To: Jeff Hill
> Cc: 'Marty Kraimer'; 'Andrew Johnson'; 'Bob Dalesio'; 'Ralph
> Lange'; 'Eric Norum'; 'Ken Evans'; 'Ned Arnold'; 'Matej
> Sekoranja'
> Subject: Re: EPICS base V4: iocCore database
> 
> On Wednesday 23 February 2005 16:48, Jeff Hill wrote:
> > > The bottom line is that unsigned types should be used only
> in
> > > the very few cases where they are essential to
> > > faithfully represent raw hardware values.
> >
> > I find that unsigned types are quite useful for situations
> where
> > the operand must never be negative. For example, with array
> > indexes this improves performance and simplifies the code
> when
> > range checking because only one side of the range check need
> be
> > done. Of course, I can't expect that everyone will agree :-)
> 
> I thought it was obvious from the context (but maybe I should
> have stated it
> explicitly) that I was only talking about record field and
> corresponding CA
> data types, not programming in general. Record field values are
> rarely used
> directly as indices into arrays and even if they would be, the
> overhead
> involved in using them would be orders of magnitude larger than
> any overhead
> due to additional range checks.
> 
> Ben



References:
Re: EPICS base V4: iocCore database Benjamin Franksen

Navigate by Date:
Prev: Re: EPICS base V4: iocCore database Benjamin Franksen
Next: Re: EPICS base V4 Benjamin Franksen
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022 
Navigate by Thread:
Prev: Re: EPICS base V4: iocCore database Benjamin Franksen
Next: RE: EPICS base V4: iocCore database Kenneth Evans, Jr.
Index: 2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·