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 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,70016ed51014902d X-Google-Attributes: gid103376,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Warning: Flame Bait Date: 1996/11/30 Message-ID: <1996Nov30.075832.1@eisner>#1/1 X-Deja-AN: 201555515 x-nntp-posting-host: eisner.decus.org references: <01bbdcb5$7500ab30$24af1486@pc-phw> x-nntp-posting-user: KILGALLEN x-trace: 849358734/29855 organization: LJK Software newsgroups: comp.lang.ada Date: 1996-11-30T00:00:00+00:00 List-Id: In article , bobduff@world.std.com (Robert A Duff) writes: > We'll see what happens. Java may well be the final nail in the coffin > for weird machines. Hmm. > > Anyway, it's hard to reason about portability "in practice". Think > about all the C programmers who write code assuming sizeof(int) = > sizeof(char*), and write code that is quite portable -- in practice. Assumptions of correspondence between "int" and pointer sizes are scheduled to be discovered as manufacturers start actually using the the 64-bit addressing capabilities of the machines they have already sold people. Those who program for DEC Unix, and then VMS, and in the future Windows NT are able to gradually discover through program execution all such (or is it really _all_, is there someplace we have not tested?) bon mots. So unlike the Java case, the hardware does not have to be "weird", it just has to be "different". I believe IBM, HP and Sun all have hardware with 64-bit addressing now, so all those C programmers out there may be kept quite busy, with half of them engaged in eliminating this error and the other half engaged in making that same old assumption in new code. Larry Kilgallen