From -3835323141181792265
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,8d9af67f0c48e4ef
X-Google-Attributes: gidf78e5,public
X-Google-Thread: fc772,8d9af67f0c48e4ef
X-Google-Attributes: gidfc772,public
X-Google-ArrivalTime: 2002-05-08 13:12:09 PST
Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!denver-snf1.gtei.net!news.gtei.net!namche.sun.com!news2me.EBay.Sun.COM!engnews1.eng.sun.com!taumet!clamage
From: Francis Glassborow <francis.glassborow@ntlworld.com>
Newsgroups: comp.std.c++,comp.lang.c++.moderated
Subject: Re: Unsignedness of size_t
Date: 8 May 2002 20:09:36 GMT
Organization: Southfield Microcomputer SS
Lines: 32
Approved: stephen.clamage@sun.com (comp.std.c++)
Message-ID: <qqILzuAxjR28EwPx@robinton.demon.co.uk>
References: <3CC7DB8F.52E75D62@bawi.org>
	<1020129034.890475@cswreg.cos.agilent.com>
 <kIroLmF3$S08EwtD@robinton.demon.co.uk>
 <1020652915.872448@cswreg.cos.agilent.com>
Reply-To: Francis Glassborow <francisG@robinton.demon.co.uk>
NNTP-Posting-Host: taumet.eng.sun.com
X-NNTP-Posting-Host: netlab.cs.rpi.edu
X-Original-Date: Wed, 8 May 2002 13:24:17 +0100
X-Submission-Address: c++-submit@netlab.cs.rpi.edu
X-Auth: PGPMoose V1.1 PGP comp.lang.c++.moderated
	iQBVAwUAPNmEe0HMCo9UcraBAQG6uwH9GRAyMl71d+SoBNfHY7rGuv30/eVJRGux
	s0K9T7oIG7OtAFP2N+mTYp17r/KvbkWn2Rp7opnj7jt1NHJNSttQ8Q==
	=K08r
X-Approved-For-Group: dom@devitto.com comp.lang.c++.moderated
X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang)
Content-Length: 1212
X-Status: $$$T
X-UID: 0000000001
Originator: clamage@taumet
Xref: archiver1.google.com comp.std.c++:11116 comp.lang.c++.moderated:42841


In article <1020652915.872448@cswreg.cos.agilent.com>, Geoff Field 
<geofffield@hotmail.com> writes
>These are worthy topics for debate.  At the moment, this thread is only

>about size_t.  However, what would you propose for clock_t and time_t?

I think I would opt for double for clock_t and long double for time_t 
but my point was that as it stands they can be any arithmetic type and 
that includes both unsigned integer types and floating point types. As 
each type has its own problems having such typedefs seems unreasonable 
to me as the problems I will have to handle are implementation specific.



-- 
Francis Glassborow      ACCU
64 Southfield Rd
Oxford OX4 1PA          +44(0)1865 246490
All opinions are mine and do not represent those of any organisation



      [ Send an empty e-mail to c++-help@netlab.cs.rpi.edu for info ]
      [ about comp.lang.c++.moderated. First time posters: do this! ]

[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.jamesd.demon.co.uk/csc/faq.html                       ]




