In article <1igx6ok.1jxrr4qncanhcN%nospam@[EMAIL PROTECTED]
>,
nospam@[EMAIL PROTECTED]
(Richard Maine) wrote:
> You can't - not with advance='no'. Sort of the whole point is that when
> a write statement completes, the result might actually be physically
> writen. The standard doesn't require that, but it is purposefully
> designed to encourage, or at least allow, that. You can't undo what has
> been written. Or, in more memorable words than mine, yet very apt:
>
> The Moving Finger writes; and, having writ,
> Moves on: nor all your Piety nor Wit
> Shall lure it back to cancel half a Line,
> Nor all your Tears wash out a Word of it
> -- Omar Khayyam
>
> Even the "half a line" bit seems perfect.
I have not used advance='no' with tabs before. If you write a
partial record, and then include a T1 at the end of the format,
would that allow you to then tab forward over the previously written
characters in subsequent write statements?
I realize that you could do the same thing with a character line
buffer, but I'm wondering if advance='no' might allow you to use the
OS buffers rather than your own internal buffers to achieve this
kind of result in an open-ended way (e.g. without knowing the
maximum record length ahead of time).
$.02 -Ron Shepard
|
