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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,7b65fc33a05f24b6 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!newsfe03.iad.POSTED!4a71828c!not-for-mail From: Hyman Rosen User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: A curiosity... References: <84d_k.82$Xt.59@newsfe13.iad> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: X-Complaints-To: abuse@WWWSpace.NET NNTP-Posting-Date: Sat, 06 Dec 2008 22:53:22 UTC Date: Sat, 06 Dec 2008 17:53:00 -0500 Xref: g2news1.google.com comp.lang.ada:2910 Date: 2008-12-06T17:53:00-05:00 List-Id: Adam Beneschan wrote: > This thread started with a comment about a tutorial that showed > students the "right" way to accomplish a certain task. What do you > want to bet that this tutorial didn't say "This works only for such- > and-such implementations" The distinction between right and wrong that the tutorial was making was about not having multiple threads access a shared object because of unpredictable timing. I doubt that there has ever been a C implementation on any architecture where it was wrong to convert a small integer to pointer and back.