Groups > comp.lang.java.programmer > #26524

Re: Possible loss of precision

X-Received	by 10.236.53.70 with SMTP id f46mr8880513yhc.17.1384704320328; Sun, 17 Nov 2013 08:05:20 -0800 (PST)
Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!n1no1476416qai.0!news-out.google.com!9ni33928qaf.0!nntp.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail
NNTP-Posting-Date	Sun, 17 Nov 2013 10:05:20 -0600
Date	Sun, 17 Nov 2013 08:05:14 -0800
From	Patricia Shanahan <pats@acm.org>
User-Agent	Mozilla/5.0 (Windows NT 5.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version	1.0
Newsgroups	comp.lang.java.programmer
Subject	Re: Possible loss of precision
References	<loss-20131113231933@ram.dialup.fu-berlin.de> <87txfe22o1.fsf@golem.phantasia.org> <kkla89tv4vb3c60ao7qkj2hr3kd0ims4gc@4ax.com> <87txfded5c.fsf@golem.phantasia.org> <1cydnYUCtYikZBvPnZ2dnUVZ_umdnZ2d@earthlink.com> <878uwnw6t1.fsf@golem.phantasia.org>
In-Reply-To	<878uwnw6t1.fsf@golem.phantasia.org>
Message-ID	<8pqdnQaCOuvddBXPnZ2dnUVZ_oSdnZ2d@earthlink.com> (permalink)
Lines	18
X-Usenet-Provider	http://www.giganews.com
NNTP-Posting-Host	70.230.195.53
X-Trace	sv3-8tN4DwqMjd/CmE7HAdVByIDg0Dfnz4F0LgTKgioykO6kh/pdWrXRMTONOFRF4oCfFlpOLrJ7njfmhNI!VgkHDyfdS6XL6OhUkJgu0R0vrKsz7hhowjBhhlTTWyYvHmpVavP4y9CSuS2iPttMfnMDxfYN/rKN!Kn/NzkskCzqLHjRonJARce7/17/XHIN3i7wPLUxyw6BM0Q==
X-Abuse-and-DMCA-Info	Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info	Otherwise we will be unable to process your complaint properly
X-Postfilter	1.3.40
X-Original-Bytes	1964
Content-Type	text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding	7bit
Xref	csiph.com comp.lang.java.programmer:26524

Show key headers only | View raw

On 11/17/2013 4:28 AM, Michael Jung wrote:
> Patricia Shanahan <pats@acm.org> writes:
...
>> On the other hand, without the special narrowing rule for
>> initializers, there would be no cast-free way of initializing a byte
>> with the value 2.
>
> They could have spent a suffix "B/b" (for non-hex integer literals) as
> with "l/L".

Why non-hex? You would still need something like the current system for
hex initialization of a byte.

The would have needed to do the the same for short, [-32768, 32767], and
for numeric initializers for char, [0, 65535].

Patricia

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Possible loss of precision Michael Jung <miju@golem.phantasia.org> - 2013-11-14 20:39 +0100
  Re: Possible loss of precision Gene Wirchenko <genew@telus.net> - 2013-11-14 15:03 -0800
    Re: Possible loss of precision Eric Sosman <esosman@comcast-dot-net.invalid> - 2013-11-14 18:31 -0500
      Re: Possible loss of precision Joerg Meier <joergmmeier@arcor.de> - 2013-11-15 00:55 +0100
      Re: Possible loss of precision Eric Sosman <esosman@comcast-dot-net.invalid> - 2013-11-14 20:19 -0500
        Re: Possible loss of precision taqmcg@gmail.com - 2013-11-15 07:01 -0800
        Re: Possible loss of precision Martin Gregorie <martin@address-in-sig.invalid> - 2013-11-15 21:36 +0000
    Re: Possible loss of precision Michael Jung <miju@golem.phantasia.org> - 2013-11-15 19:24 +0100
      Re: Possible loss of precision Patricia Shanahan <pats@acm.org> - 2013-11-15 20:48 -0800
        Re: Possible loss of precision Michael Jung <miju@golem.phantasia.org> - 2013-11-17 13:28 +0100
          Re: Possible loss of precision Patricia Shanahan <pats@acm.org> - 2013-11-17 08:05 -0800

csiph-web