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.3 required=5.0 tests=BAYES_00,INVALID_MSGID,
	MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9e47ad8d460f46b8
X-Google-Attributes: gid103376,public
From: jmoor@my-deja.com
Subject: Re: Extracting Fields in Files
Date: 2000/01/13
Message-ID: <85l0iu$6uj$1@nnrp1.deja.com>#1/1
X-Deja-AN: 572136718
References: <200001130658.HAA07055@bulgaria.otn.eurocopter.de>
X-Http-Proxy: 1.0 DCC-PROXY,
 1.0 x37.deja.com:80 (Squid/1.1.22) for client 209.49.118.18
Organization: Deja.com - Before you buy.
X-Article-Creation-Date: Thu Jan 13 17:04:40 2000 GMT
X-MyDeja-Info: XMYDJUIDjmoor
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
Date: 2000-01-13T00:00:00+00:00
List-Id: <comp.lang.ada>

Would you believe that I am reading a variable length record created on
a Unisys machine whose records are in the following sequence:

record    size
  #       (bytes)

1          16
2         212
3          16
4         212
5          16
6         212
7          16
8         212
9          16

I open the file with the following statement;
  text_io_open ( file => tip0125,
       mode => text_i.in_file,
       name => "tip0125");

Every time I read the file with the following statement;
  get_line (file => tip0125,
      item => rec01,
      last => rec01_length,)

After each 212 byte record is read, the get_line goes through a cycle
where it believes a zero byte record has been read.  I can easily get
around the problem by testing "rec01_length" for zero bytes, but this
is evidence that I might not understand the nature of the "get_line"
command when reading a variable length file.


Sent via Deja.com http://www.deja.com/
Before you buy.