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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,a0833bbed8752e1f
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local1.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail
NNTP-Posting-Date: Fri, 29 Oct 2004 16:50:55 -0500
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
References: <ba2f9c57.0410210952.438515d@posting.google.com>
 <1861614.TWv5A9FgVL@linux1.krischik.com>
 <4178e979_1@baen1673807.greenlnk.net>
 <1195374.UMjBCk7lO1@linux1.krischik.com>
 <UDSed.6962$d5.59024@newsb.telia.net>
 <1154613.ipZcUgduzp@linux1.krischik.com>
 <PaSdnX0j54BWCeDcRVn-jA@megapath.net>
 <a4wfd.3107$kM.1044@newsread3.news.pas.earthlink.net>
 <o-CdnddJwfPP6hzcRVn-pw@megapath.net> <39q24nDZNOOB@eisner.encompasserve.org>
Subject: Re: variable lenght strings
Date: Fri, 29 Oct 2004 16:52:24 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Message-ID: <EuqdnfTh9oXdJh_cRVn-2Q@megapath.net>
NNTP-Posting-Host: 64.32.209.38
X-Trace: 
 sv3-FUxa3SzuDO2+Z7zlORRpeW+HqJy7p5cvrvK52tI3sO0R9v8u2Rvyvsu88awY4CZmP0dCBlSsyfQK6rZ!y6I43EU0a5RCbmXOxEdGlWmepKXo8HItlIxgmfd3WLlduostqC+vDpempvETpS6YG/Yfkj6WslB2
X-Complaints-To: abuse@megapath.net
X-DMCA-Complaints-To: abuse@megapath.net
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.20
Xref: g2news1.google.com comp.lang.ada:5895
Date: 2004-10-29T16:52:24-05:00
List-Id: <comp.lang.ada>

"Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message
news:39q24nDZNOOB@eisner.encompasserve.org...
> In article <o-CdnddJwfPP6hzcRVn-pw@megapath.net>, "Randy Brukardt"
<randy@rrsoftware.com> writes:
>
> > Huh? A null line without a line terminator would be indistinguishable
from a
> > line terminator at the end of a file. So it is perfectly reasonable for
an
> > implementation to treat this as reading past the end of a file
(Janus/Ada
> > certainly does too). Indeed, I'd argue that it is impossible for there
to be
> > a null line without a line terminator at the end of a file.
>
> So on this general subject, how do implementations which use a special
> character for line termination handle the situation where that character
> is in the middle of a line ?  Is there a special escape character to
> mean "the next character is real" ?  Is that special escape character
> the same for all implementations ?

There's no requirement that the line terminator character(s) (if that's how
its done) be allowed in the middle of a line. A.10(8) says that the effect
of Get or Put of control characters other than TAB is not specified by the
language. So Put(LF) can be read as a line terminator, or raise
Program_Error, or whatever.

                      Randy.