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=-0.1 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM,PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Thread: a07f3367d7,c689b55786a9f2bd
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news2.google.com!news3.google.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!193.201.147.78.MISMATCH!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!.POSTED!not-for-mail
From: Warren <ve3wwg@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: for S'Image use Func??
Date: Tue, 11 May 2010 16:56:05 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <Xns9D75839465A14WarrensBlatherings@81.169.183.62>
References: <Xns9D7085FECB88EWarrensBlatherings@188.40.43.213>
 <op.vcaqajn0ule2fv@garhos> <Xns9D70A3756AAE0WarrensBlatherings@188.40.43.213>
 <wccmxwcu6kc.fsf@shell01.TheWorld.com> <op.vcaxs1h4ule2fv@garhos>
 <wcceihou455.fsf@shell01.TheWorld.com>
 <hs0jm5$vr4$1@news.eternal-september.org>
 <wcchbmjlx6a.fsf@shell01.TheWorld.com>
 <4be417b4$0$6992$9b4e6d93@newsspool4.arcor-online.net>
 <wccpr17yeji.fsf@shell01.TheWorld.com>
 <Xns9D747817630D6WarrensBlatherings@188.40.43.245>
 <zvtps4jzmo1z$.mzhapf4p7b4a.dlg@40tude.net>
 <Xns9D7482F0549D2WarrensBlatherings@188.40.43.245>
 <1qcb6z4i20dyb.1dz2hd4c0vx69.dlg@40tude.net>
 <Xns9D7496E77C7B0WarrensBlatherings@188.40.43.245>
 <84r4k5Ftk8U1@mid.individual.net>
 <Xns9D74A5958E4B8WarrensBlatherings@188.40.43.245>
 <84sfkjF3btU1@mid.individual.net> <op.vci60tiexmjfy8@garhos>
Injection-Date: Tue, 11 May 2010 16:56:05 +0000 (UTC)
Injection-Info: mx01.eternal-september.org;
 posting-host="9f8M0iN5t54V+4DF/iqO8g";
	logging-data="28153"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19b5rT8ba8R+g433yTKH6EM2n4CtfoIBQY="
User-Agent: Xnews/5.04.25
X-Face: 
 &6@]C2>ZS=NM|HE-^zWuryN#Z/2_.s9E|G&~DRi|sav9{E}XQJb*\_>=a5"q]\%A;5}LKP][1mA{gZ,Q!j
Cancel-Lock: sha1:/l7NqXgeSWy1n5/NUo3UJIG1QAs=
Xref: g2news2.google.com comp.lang.ada:11508
Date: 2010-05-11T16:56:05+00:00
List-Id: <comp.lang.ada>

=?iso-8859-15?Q?Yannick_Duch=EAne_=28Hibou57=29?= expounded in
news:op.vci60tiexmjfy8@garhos: 

> Le Tue, 11 May 2010 09:34:42 +0200, Niklas Holsti  
> <niklas.holsti@tidorum.invalid> a �crit:
>> Yes, with one problem, which is that it is hard (that is, I don't
..
> I was to say this is a matter only with Standard_Input, and in the
> context  of "/dev/null" which you gave, you have no need to open
> "/dev/null" as a  file of lines if have no reason to think "/dev/null"
> is indeed a file of  lines.

But feed that same program with 2 empty lines,
and the program reports:

$ ./linelen <t.t
Line 1 has 0 characters.

This is clearly defective. It either returns null lines
or it doesn't. Here we have a bit of both (a "Microsoft
solution" ;-)

> The only remaining case is the one of the standard input.

"Standard input" (emphasis on "standard") has nothing to
do with it.  Whether you read it as standard input or
from a "non-standard" source, it behaves the same way.

The file I used above, is a well formed text file. 

$ wc -l t.t
2 t.t

yet the program only sees 1 line. Not a huge problem- 
just a little wart.

But the real question is- is this a design or 
implementation wart?

Warren