Kay-Uwe Kasemir wrote:
Bottom line: the supported well-known primitive data types and the
types that a certain implementation of dataAccess implements in its
interface functions are two pairs of things.
Hi Ralph!
two pairs = 4 things ?
Oops, I'm sorry. Of course: Times the number of participating developers.
36 things? 40 things?
Ralph
- References:
- RE: V4 design issue: Should primitive data types have well defined precisions? Dalesio, Leo `Bob`
- Re: V4 design issue: Should primitive data types have well defined precisions? Ralph Lange
- Re: V4 design issue: Should primitive data types have well defined precisions? Marty Kraimer
- Re: V4 design issue: Should primitive data types have well defined precisions? Ralph Lange
- Re: V4 design issue: Should primitive data types have well defined precisions? Kay-Uwe Kasemir
- Navigate by Date:
- Prev:
dataAccess V4 Ca client propertyId questions Marty Kraimer
- Next:
Re: V4 design issue: Should primitive data types have well defined precisions? Marty Kraimer
- Index:
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: V4 design issue: Should primitive data types have well defined precisions? Kay-Uwe Kasemir
- Next:
Re: V4 design issue: Should primitive data types have well defined precisions? Marty Kraimer
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|