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,5697899e4423465c X-Google-Attributes: gid103376,public From: eachus@spectre.mitre.org (Robert I. Eachus) Subject: Re: null pointer representation (was: Boolean Representation) Date: 1998/10/02 Message-ID: #1/1 X-Deja-AN: 397124067 References: <6umkbn$pv5$1@nnrp1.dejanews.com> <6uo7p6$dk4$1@nnrp1.dejanews.com> Organization: The Mitre Corp., Bedford, MA. Newsgroups: comp.lang.ada Date: 1998-10-02T00:00:00+00:00 List-Id: In article Keith Thompson writes: > Even if there weren't any such machines, I don't believe that the > assumption that System.Null_Address is all zero bits would be > justified -- though admittedly my argument would be a bit weaker. Some years back at Stratus, we used one not zero as the value for null pointers, since it trapped if dereferenced. When the 68020 came along, we temporarily switched to xFFFFFFFF (I don't think that version ever shipped.) Then to a version of the OS where page zero was inaccessable in user mode so that we could use zero as a null address in user code. -- Robert I. Eachus with Standard_Disclaimer; use Standard_Disclaimer; function Message (Text: in Clever_Ideas) return Better_Ideas is...