Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!weretis.net!feeder4.news.weretis.net!feeder2.ecngs.de!ecngs!feeder.ecngs.de!nx01.iad01.newshosting.com!newshosting.com!69.16.185.21.MISMATCH!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!spln!extra.newsguy.com!newsp.newsguy.com!news3
From: jmfbahciv <See.above@aol.com>
Newsgroups: comp.arch,alt.folklore.computers
Subject: Re: Solving the Floating-Point Goldilocks Problem!
Date: 20 Oct 2011 13:38:29 GMT
Organization: "Have EDDT, will travel"
Lines: 20
Message-ID: <PM0004AFBAEC3652DC@ac81532f.ipt.aol.com>
References: <j3of5s$gad$1@gosset.csi.cam.ac.uk> <j3of5s$gad$1@gosset.csi.cam.ac.uk> <cf3834e8-ac6b-4f5e-b94b-54e576c1f3cc@g30g2000vbu.googlegroups.com> <j3osgq$d9m$2@dont-email.me> <cm2067dltqpvfagestfnci7c1qo460vluk@4ax.com> <1319.297T1386T264355@kltpzyxm.invalid> <4E60C6B7.40309@SPAM.comp-arch.net> <8ht167tjg1dg9e22ekkf46dhfud0am962g@4ax.com> <j3r9hq$5e5$1@dont-email.me> <j3of5s$gad$1@gosset.csi.cam.ac.uk> <cf3834e8-ac6b-4f5e-b94b-54e576c1f3cc@g30g2000vbu.googlegroups.com> <j3osgq$d9m$2@dont-email.me> <cm2067dltqpvfagestfnci7c1qo460vluk@4ax.com> <1319.297T1386T264355@kltpzyxm.invalid> <4E60C6B7.40309@SPAM.comp-arch.net> <8ht167tjg1dg9e22ekkf46dhfud0am962g@4ax.com> <j3r9hq$5e5$1@dont-email.me> <8639gek6lo.fsf@zipcon.net> <PM0004AC0A5C77E22C@aca221f7.ipt.aol.com> <j7n0jf$5nb$1@news.task.gda.pl>
NNTP-Posting-Host: p6a92eaa1664a8d6fdc2e4ae94ae053d28e97986f71c2a72a.newsdawg.com
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
User-Agent: Pineapple News/0.9.0 (Mac OS X 10.4.9 PowerPC)
X-Registered-To: [Registered Name]
X-Program-URL: http://www.platinumball.net/pineapple/news/macosx/
Xref: x330-a1.tempe.blueboxinc.net comp.arch:4282

Piotr Wyderski wrote:
> jmfbahciv wrote:
>
>
>>>> 34587706689349 times.
>>>>
>>>> It sure makes it hard to read and there is no excuse for that.  I
>>>> realize there are issues with commas versus spaces as separators, but
>>>> these could be overcome.
>>>
>>> Even if they use spaces instead of commas, it's still easier to read
>>> than no separators at all.
>>
>> Not spaces..  Which do you chose?
>
> 123_456_789

Which could be interpreted as a bit shift character.

/BAH