From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.107.153.71 with SMTP id b68mr2013272ioe.9.1472034848961; Wed, 24 Aug 2016 03:34:08 -0700 (PDT) X-Received: by 10.157.29.252 with SMTP id w57mr141129otw.16.1472034848927; Wed, 24 Aug 2016 03:34:08 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!f6no12561046ith.0!news-out.google.com!d68ni37463ith.0!nntp.google.com!f6no12537137ith.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 24 Aug 2016 03:34:08 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2601:191:8302:3f70:a9ad:2efe:1ecf:5bb1; posting-account=fdRd8woAAADTIlxCu9FgvDrUK4wPzvy3 NNTP-Posting-Host: 2601:191:8302:3f70:a9ad:2efe:1ecf:5bb1 References: <07632b3f-f419-4865-a8f8-01b568a6883e@googlegroups.com> <2d96f593-e1d3-43da-9a6a-16e8ce0f675b@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Why does this input get "skipped"? From: rieachus@comcast.net Injection-Date: Wed, 24 Aug 2016 10:34:08 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:31536 Date: 2016-08-24T03:34:08-07:00 List-Id: On Tuesday, August 23, 2016 at 2:23:05 AM UTC-4, J-P. Rosen wrote: > Le 23/08/2016 =C3=A0 00:18, rieachus@comcast.net a =C3=A9crit : > > Get_Line, Skip_Line, and Set_Col(1) should all get you to the same plac= e.=20 > Not exactly. The benefit of using Set_Col(1) is that if you are already > on column 1, it does nothing, while others will go to the next line. >=20 > Therefore, Set_Col(1) can safely ignore whether there was a skip_line > preceding it or not. Correct. I was only considering situations following a non-blank Put. I j= ust consider it to be very bad juju to write output without completing the = line. I haven't checked recently, but it used to be that compiler run-time= s would not immediately read a partial/non-completed line. (The buffering = is usually in the operating system. The real issue is that you can't close= then reopen Current_Input in an immediate mode.)