Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.fsmpi.rwth-aachen.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Daniele Futtorovic Newsgroups: comp.lang.java.programmer Subject: Re: BlueJ Coding Help Date: Mon, 02 Sep 2013 13:53:27 +0200 Organization: A noiseless patient Spider Lines: 67 Message-ID: References: <87e3fd5b-cd93-4c50-bef4-05d9cf49ab0f@googlegroups.com> <5223c151$0$298$14726298@news.sunsite.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 2 Sep 2013 11:53:40 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="7ce81157ec2018035dc858e4d5a27b14"; logging-data="28434"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+6lCZTSF2NwlHKcnOJ9IAz" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 In-Reply-To: <5223c151$0$298$14726298@news.sunsite.dk> Cancel-Lock: sha1:pLEtmXYffZ8EiLQ3sJHaeirt+xY= Xref: csiph.com comp.lang.java.programmer:25209 On 2013-09-02 00:35, Arne Vajhøj allegedly wrote: > On 9/1/2013 9:47 AM, Daniele Futtorovic wrote: >> On 2013-09-01 11:05, Jukka Lahtinen allegedly wrote: >>> Daniele Futtorovic writes: >>>> On 2013-08-31 17:30, Jukka Lahtinen allegedly wrote: >>>>> ram@zedat.fu-berlin.de (Stefan Ram) writes: >>>>>> Jukka Lahtinen writes: >>>>>>> The method System.out.println always adds a linefeed >>>>>>> at the end of the >>>>>>> output, and you add one yourself with the \n. >>> >>>>>> "\n" might not be the system's line separator. >>> >>>>> True, but is there a system where it doesn't cause a linefeed? >>> >>>> Macintoshes, pre-OS X if I'm not mistaken, used \r (carriage return) as >>>> the line separator. >>> >>> I thought they use LF and CR (in that order, opposite to the DOS world), >>> not only the CR. I never used them myself, don't they do anything with >>> just a LF that doesn't come with CR? >> >> No, just the carriage return. >> >> I do not know what they would have done with a line feed, sorry. For my >> practical purposes, MacOS has always been ancient history (as opposed to >> OSX, which uses LF). >> >> They just use the carriage return. It's one of those things you just >> pick up. Because whenever the geeks ramble, like old cow-boys around the >> fire, multiple parallel soliloquies, and one of them ever-so-slightly >> implicitly associates the EOL sequence with a LF character, you'll >> invariably have one of the thither silent ones jump up and interject: >> "Tut tut tut, LF might /not be/ the line separator", in an ominous tone. >> And then the one who made the association falls silent, for he knows he >> has sinned; and then all the greenhorns perk up, ravished by this new >> mysterious development; and they press the old hands with questions, to >> pierce the mystery. A satisfied smile settles on the faces of the old >> hands, and after a little pressing (etiquette obliges), they will go >> into lively discussions about ye olden days (discussions which might >> actually, but not necessarily, address the mystery at hand)... which I'd >> personally love to do, 'cause it's fun and it's knowledge, but can't, so >> I'm just giving you the meta. > > I think that description is rather accurate. > > But I still think that it is relevant to bring it up. > > There are certain things about portability that developers > should learn at some point. > > LF terminated, CRLF terminated, CR terminated, count prefix, > count prefix & suffix variable length line formats. > > Little and big endian. > > IEEE floating point and other floating point formats. > > Unicode, UTF-8, UTF-16, ISO-8859-1, ASCII, EBCDIC for text. > > Etc. In case it wasn't clear from the above: wholeheartedly agreed, and I love those discussions, and was just frustrated by my inability to do it myself. :)