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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1014db,582dff0b3f065a52 X-Google-Attributes: gid1014db,public X-Google-Thread: 109fba,582dff0b3f065a52 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,bc1361a952ec75ca X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-27 12:35:22 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!tor-nx1.netcom.ca!tor-nn1.netcom.ca.POSTED!not-for-mail Message-ID: <3B8AA131.3FCC0E9A@yahoo.com> From: Joe Maun Organization: H X-Mailer: Mozilla 4.77 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++ Subject: Re: Subtle Bugs, kudos Ada (was How Ada ...Red Code ...) References: <3B6555ED.9B0B0420@sneakemail.com> <87n15lxzzv.fsf@deneb.enyo.de> <3B672322.B5EA1B66@home.com> <4a885870.0108112341.7ce02ac0@posting.google.com> <3B834E5D.B0D26AB1@adaworks.com> <9lvsic$bet9s$1@ID-9852.news.dfncis.de> <9m0193$grs$1@bird.wu-wien.ac.at> <3B83F042.4CFB073D@home.com> <3B8462C8.5596C089@yahoo.com> <87n14nmbf8.fsf@deneb.enyo.de> <3B89A809.46083436@yahoo.com> <871ylxpxu6.fsf@deneb.enyo.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 27 Aug 2001 15:36:17 -0400 NNTP-Posting-Host: 216.123.137.218 X-Complaints-To: abuse@attcanada.ca X-Trace: tor-nn1.netcom.ca 998940907 216.123.137.218 (Mon, 27 Aug 2001 15:35:07 EDT) NNTP-Posting-Date: Mon, 27 Aug 2001 15:35:07 EDT Xref: archiver1.google.com comp.lang.ada:12485 comp.lang.c:77074 comp.lang.c++:86048 Date: 2001-08-27T15:36:17-04:00 List-Id: Florian Weimer wrote: > > Joe Maun writes: > > >> > This doesn't matter in this case. The value that the vacated bits take > >> > is indeed implementation defined, but the sign bit must reliably be > >> > shifted into the required position, since nothing frees it from the > >> > requirement that "The result of E1 >> E2 is E1 right-shifted E2 bit > >> > positions". > >> > >> What about sign/magnitude representation of signed integers? > > > > What about them? > > The sign bit won't be shifted right, so you can't extract it using the > method given above. I fail to see your point. Why wouldn't the sign bit be shifted right in sign magnitude representation? The quote from the standard above seems clear - and it applies to a signed magnitude implementation as well. -- Joe Maun Montreal, QC Canada