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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,610e53a911ec64b3 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-25 18:38:01 PST Path: nntp.gmd.de!news.rwth-aachen.de!news.rhrz.uni-bonn.de!RRZ.Uni-Koeln.DE!uni-duisburg.de!zib-berlin.de!news.mathworks.com!zombie.ncsc.mil!admii!cmcl2!thecourier.cims.nyu.edu!thecourier.cims.nyu.edu!nobody From: dewar@cs.nyu.edu (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: Importing C Structures Date: 25 Mar 1995 13:07:53 -0500 Organization: Courant Institute of Mathematical Sciences Message-ID: <3l1m5p$pok@gnat.cs.nyu.edu> References: <3kr4q3$jd9@newsflash.concordia.ca> <3ksg66$h1c@newssvr.cacd.rockwell.com> NNTP-Posting-Host: gnat.cs.nyu.edu Date: 1995-03-25T13:07:53-05:00 List-Id: Another way to deal with giving different names for reading and writing the same memory location would simply be to rename it with appropriate names, and then by convention use the appropriate name. This wouldn't enforce the right name use, but would permit it, and that may be perfectly good enough. One doesn't always need enforce mechanisms for ensuring that one's own code is not incompetently written :-)