2002 2003 2004 <2005> 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 <2005> 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: V4 design issue: Should primitive data types have well defined precisions? |
From: | Marty Kraimer <[email protected]> |
To: | EPICS Core Talk <[email protected]> |
Date: | Wed, 22 Jun 2005 06:38:26 -0500 |
I will argue that the answer should be yes.epicsTypes is the proposed set of primitive types are well as proposed definition for string, array, and enum.
Without agreeing on a set of primitive data types, including the precision of each type, mismatches between data sources and consumers can easily occur.
Corba IDL, Java, and C# all use types short, int, long, float, and double but ALL define the exact precision for each. In fact they all use the sdame precision, i.e.
short 16 bits int 32 bits long 64 bits float 32 bit IEEE float double 64 bit IEEE float. Marty