Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: BlueJ Coding Help Date: Sat, 31 Aug 2013 11:26:43 -0400 Organization: A noiseless patient Spider Lines: 24 Message-ID: References: <87e3fd5b-cd93-4c50-bef4-05d9cf49ab0f@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Sat, 31 Aug 2013 15:26:45 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="0d73d8cc209bff1c6395088b400d0605"; logging-data="12901"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+Ok48Nt/2NNsaAH7zjshH7" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 In-Reply-To: Cancel-Lock: sha1:yOseAt0/O+mU04SdNAxLqmpWKS8= Xref: csiph.com comp.lang.java.programmer:25181 On 8/31/2013 9:46 AM, Stefan Ram wrote: > Jukka Lahtinen writes: >> The method System.out.println always adds a linefeed > > the system's line separator > >> at the end of the >> output, and you add one yourself with the \n. > > "\n" might not be the system's line separator. Is it just me, or are others also peeved that PrintStream always ends lines with the system's line separator? IMHO, the separator should be choosable on a stream-by-stream basis, so (for example) one could easily write through a PrintStream to a socket protocol requiring \r\n no matter what the local system uses. Ah, well. The horse and barn have been nonproximate for a long time now. -- Eric Sosman esosman@comcast-dot-net.invalid