From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7b69a8818c20ab9f X-Google-Attributes: gid103376,public From: Robert Dewar Subject: Re: Y21C Bug Date: 2000/01/04 Message-ID: <84t8qk$b9q$1@nnrp1.deja.com>#1/1 X-Deja-AN: 568164340 References: <84nqbo$q28$1@nnrp1.deja.com> <84o0g2$u8v$1@nnrp1.deja.com> <84pvrs$7q1@ftp.kvaerner.com> X-Http-Proxy: 1.0 x31.deja.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Tue Jan 04 16:58:05 2000 GMT X-MyDeja-Info: XMYDJUIDrobert_dewar Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.61 [en] (OS/2; I) Date: 2000-01-04T00:00:00+00:00 List-Id: In article , Robert A Duff wrote: > And from what I've heard, making Unix code "64-bit clean" > hasn't been so easy, which is exactly the sort of thing Robert > Dewar was talking about. Indeed it is a HUGE effort to make some code 64-bit clean, and my guess is that unices will support 32-bit code for a long time, and it will be a bad earthquake when there is a requirement to change legacy 32-bit code to make it 64-bit compatible (as will possibly happen at the date blow up time (which will happen in our life times for at least some of us). > If it were as easy as changing some "Word_Size" constant, then > people wouldn't have invented a fancy term like "64-bit clean" > for it. ;-) Sent via Deja.com http://www.deja.com/ Before you buy.