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.1 required=5.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,ec21c3c7cdc7ff3e X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!news2.google.com!news4.google.com!news.glorb.com!news-xxxfer.readnews.com!news-out.readnews.com!spool-big1.readnews.com!not-for-mail Newsgroups: comp.lang.ada Subject: Re: private types From: "Peter C. Chapin" References: <1142279908.327131.230200@j52g2000cwj.googlegroups.com> <1259548.CMTukHGvVZ@linux1.krischik.com> Organization: Kelsey Mountain Software Message-ID: User-Agent: Xnews/5.04.25 Date: 19 Mar 2006 22:11:24 GMT NNTP-Posting-Host: f780ff4a.news.sover.net X-Trace: DXC=SLloLOE6SL8H?Hj@=S0E9 Bj�rn Persson wrote in news:SteTf.48935$d5.205176@newsb.telia.net: > Well, does the standard require that (void*)0 == NULL? What if I > wanted a pointer to address zero on this hypothetical OS? How would I > get that if (void*)0 gets transformed to a non-zero NULL? I'd have to review the precise definition of the null pointer constant. Anything other than that is treated in the "usual" way. So for example, this might work const int p = 0; ... (void*)p ... Or maybe you need to take the 'const' off the declaration of p. Peter