Prev: Facing exception: Invalid byte 2 of 4-byte UTF-8 sequence.
Next: redirect System.out to JTextArea
From: Arved Sandstrom on 23 Jan 2010 09:04
John B. Matthews wrote:
> In article <hjdsgh$2tt$2(a)news.albasani.net>, Lew <noone(a)lewscanon.com>
> wrote:
>
>> Lew wrote, quoted or indirectly quoted someone who said :
>>>> Why in the world would you assign to 'null' first, then discard that
>>>> initialization immediately?
>> Roedy Green wrote:
>>> If you use IntelliJ, it quickly slaps your wrist for any unnecessary
>>> initialisation.
>> Doesn't FindBugs also report that sort of thing?
>
> I don't see it:
>
> <http://findbugs.sourceforge.net/bugDescriptions.html>
>
More to the point, I can't make FindBugs complain about it in a simple
test case. javap confirms that the unnecessary initialization is present
in the bytecode, so FB sees it. PMD also apparently does not complain
about this.

AHS
From: Lars Enderin on 23 Jan 2010 10:29
Roedy Green wrote:
> On Fri, 22 Jan 2010 23:12:09 -0500, Lew <noone(a)lewscanon.com> wrote,
> quoted or indirectly quoted someone who said :
>
>> My newsreader displays those as spaces.
>
>
> The post is question is :
>
> Path:
> forte-easynews!core-iad-easynews!news-in-02-iad.easynews.com!news.easynews.com!s03-b12.iad!npeersf01.iad.highwinds-media.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!c4g2000yqa.googlegroups.com!not-for-mail
> From: Lew <lew(a)lewscanon.com>
> Newsgroups: comp.lang.java.programmer
> Subject: Re: Speeding up reading from files
> Date: Thu, 21 Jan 2010 11:33:21 -0800 (PST)
> Organization: http://groups.google.com
> Lines: 58
> Message-ID:
> <c0c78881-45b6-4af8-a7d8-e25d979d7fd2(a)c4g2000yqa.googlegroups.com>
> References: <f0bgl5ldr1nes1gpcukce44dpb4bmv4edj(a)4ax.com>
> NNTP-Posting-Host: 129.42.208.177
> Mime-Version: 1.0
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> X-Trace: posting.google.com 1264102401 30870 127.0.0.1 (21 Jan 2010
> 19:33:21 GMT)
> X-Complaints-To: groups-abuse(a)google.com
> NNTP-Posting-Date: Thu, 21 Jan 2010 19:33:21 +0000 (UTC)
> Complaints-To: groups-abuse(a)google.com
> Injection-Info: c4g2000yqa.googlegroups.com;
> posting-host=129.42.208.177;
> posting-account=IZs2IgoAAACGaj2oD74Zp9JDhkUk-os6
> User-Agent: G2/1.0
> X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> rv:1.9.1.7)
> Gecko/20091221 Firefox/3.5.7 (.NET CLR
> 3.5.30729),gzip(gfe),gzip(gfe)
> Xref: core-iad-easynews comp.lang.java.programmer:302948
> X-Received-Date: Thu, 21 Jan 2010 19:34:21 UTC (s03-b12.iad)
>
> The line in question is:
>
>> =A0 =A0 =A0 =A0 =A0 =A0 BufferedReader in =3D null;
>
> It was posted via Google Groups using Quoted Printable.
>
> I want to be sure the fault is with my Newsreader, Agent, not, Google
> Groups or some other weak link in the chain.
>
> Who sees the ORIGINAL post with spaces prior to BufferedReader?
>
> Who sees the ORIGINAL post with =A0?
>
>
> The ORIGNIAL ORIGNAL post was:
> Path:
> forte-easynews!core-iad-easynews!news-in-02-iad.easynews.com!news.easynews.com!s02-b52!npeersf01.iad.highwinds-media.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.brightview.co.uk!news.brightview.co.uk.POSTED!not-for-mail
> NNTP-Posting-Date: Thu, 21 Jan 2010 04:31:11 -0600
> From: Mark <i(a)dontgetlotsofspamanymore.invalid>
> Newsgroups: comp.lang.java.programmer
> Subject: Speeding up reading from files
> Date: Thu, 21 Jan 2010 10:31:04 +0000
> Reply-To: y5ojlnx02(a)sneakemail.com
> Message-ID: <f0bgl5ldr1nes1gpcukce44dpb4bmv4edj(a)4ax.com>
> X-Newsreader: Forte Agent 3.3/32.846
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> User-Agent: Hamster/2.1.0.11
> Lines: 34
> X-Usenet-Provider: http://www.giganews.com
> X-Trace:
> sv3-saTZPZFF5hu8ID3Id9lDnXlaRqb9wKMlglGUKXG2dJNuCtOHO5IG8VJ+SM2tpk28XP3t20G+xcdnTu0!VCR204Z7znEAg0ccfxLWpWm4o2rvUnUEcJZZdbfS4UWIEYDTOHt7d3RJLxyZsmuAHtM3dthCyv58!tz3h7DwXcgEfoaiH
> 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
> Bytes: 2234
> Xref: core-iad-easynews comp.lang.java.programmer:302906
> X-Received-Date: Thu, 21 Jan 2010 10:31:11 UTC (s02-b52)
>
> the relevant line is:
> BufferedReader in = null;
>
>
> It was posted via Hamster using Plain text.
>
>
> Who sees the ORIGINAL ORIGINAL post with spaces prior to
> BufferedReader? What newsreader are you using?

> Who sees the ORIGINAL ORIGINAL post with =A0?
> What newsreader are you using?

Nobody should see any =A0 there. Those characters are inserted by Google
in *quoted* text when it's exported to the real Usenet. If you use GG to
read Usenet posts and look at the frame source, you'll find that they
use &nbsp; and <br> to make the browser show the text just like it was
received. If you post from GG, they seem to remember what you wrote and
don't insert any &nbsp; or its QP equivalent =A0 for your original
spaces, but quoted text is treated differently.

> Does what the newserver send you? Does it contain non-breaking spaces
> A0 or regular spaces.
>
> -----------
>
> In Fort� Agent I see the ORIGINAL post with =A0 displayed on the
> screen.

Probably because Fort� does not realize that =A0 is QP for &nbsp;.
Thunderbird does, for example.

> I see the ORIGINAL ORIGINAL post with plain spaces.

Because there are no other spaces there.
From: RedGrittyBrick on 25 Jan 2010 06:15

Roedy Green wrote:
> On Thu, 21 Jan 2010 11:33:21 -0800 (PST), Lew <lew(a)lewscanon.com>
> wrote, quoted or indirectly quoted someone who said :
>
>>> =A0 =A0 =A0 =A0 =A0 =A0 in =3D new BufferedReader(new InputStreamReader(n=
>
> those A0s are &nbsp;s
> char( 160 );
>
> Agent quietly converted them to ordinary spaces, but I gather's Lew's
> newsreader converter them to =A0
>
> Newsreaders tend to be pretty flat footed when interpreting text. Best
> to keep your posts to printable ASCII.

I intend to continue to use ISO-8859-1 and UTF8.

--
RGB
First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: Facing exception: Invalid byte 2 of 4-byte UTF-8 sequence.
Next: redirect System.out to JTextArea