Re: EOF

[Carlo Caballero Carlo.Caballero@xxxxxxxx]

Hi, Annie!

Somewhat belatedly responding to your commentary...

On Sat, 13 Mar 1999, ... wrote:
>
> Hi, Carlo. The most common way these days is merging
> a downloaded file that was created by a dos word processor
> and uploaded to the 'net using a binary protocol, thus
> retaining the EOF char. More often than not, the word
> processor was xyWrite. (It's a safe guess, e.g., that
> the many Nando files that end with an EOF at some point
> were saved in xyW.) Has some or all of your file been
> on another platform sometime?
>

No, it never left XyWrite, nor was anything added to it except as text
within XyWrite.

>
> XyWrite 4 has a setting (d 1A=1) that neutralizes midfile
> EOFs, but docs warn against using the setting as a default
> (for reasons that become obvious if you do). Normally, you'd
> turn to it only you were aware of a file size discrepancy--
> as you were, but that's not always the case.
>

This is interesting. Could I have aborted the file, quit XY3, started up
XY4, reset this default, called up the XY3 file and deleted the midfile
EOF, set the default back to zero, and finally saved? I'm not sure
exactly what you mean by "neutralize."

Between your FIZFIX1A for XY3 and the XYWWWeb program for XY4, I'll have
lots of alternatives next time. Thanks for the description of your
program.

>
> My xpl file-opener "do"es FIZFIX1A to every file I edit,
> and my EOF headaches are a faded memory. The "do" is
> invisible unless FIZFIX1A zaps a midfile EOF, in which
> case the xpl manager issues a prompt of the former and
> current displayed size length, pausing for a key press.
> FIZFIX1A leaves the e-o-f EOF alone unless instructed to
> remove it when a file is closed, as is desirable of course
> for uploads that will use a binary protocol. (xyW4 afaik
> has no built-in way either to rid a file of the e-o-f
> EOF, but you can do that with a simple dos copy command.)
> Hmmm, come to think of it, if a midfile EOF is present
> FIZFIX1A may take off the e-o-f EOF too, but if so all
> you need do to get a new one is save the file again
> in xyW after destructive EOFs are gone; XyW gives you
> only one e-o-f EOF.
>

That last bit is worth remembering.

> ≪ I never remember having trouble with the file, but
> I wonder if XyWrite didn't break it into two or three
> pieces and then reassemble it wrong ... ≫
>
> I don't think so. ;) C'mon, Carlo. Have you ever known
> xyW3.56 to do anything else that flaky? ... Ciao. 	--a
>

Well... It *has* happened before, but I don't know if the problems had to
do with EOFs.

Best,
Carlo

\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__\__

                 
Carlo Caballero, Ph.D.
Research Associate
College of Music
Campus Box 301
The University of Colorado
Boulder, CO 80309

thyrsus@xxxxxxxx

"Let's face it: dead people are busier than ever."