Re: List-directed input with no <CR> on last record
- From: gary.l.scott@xxxxxxxx
- Date: 7 Jun 2006 10:55:13 -0700
glen herrmannsfeldt wrote:
Richard E Maine wrote:
(snip)
I can believe that there are editors that do it that way. But I consider
that a bug. I can imagine no intentional design rationale that would
suggest it was a good idea to turn an empty file with no records into a
file with one empty record. I think that's just a classic "failure to
look at the boundary case" bug in implementation.
There might be files systems that can't support zero length files,
or zero length lines in files. CMS has some unusual restrictions, but I
can't remember then right now.
In the record oriented file system CMS does not allow a file of size
zero. In the byte file system, the rules are virtually (if not
completely) identical to unix. In the record oriented file system,
even with variable length record format, a text-oriented file will be
saved with a single space character if you attempt to delete all
content. During an edit session, the default is a pad of space
characters as if it were of fixed length record type of length 80
characters (trailing spaces are truncated on saving by default for text
(or html) files).
-- glen
.
- References:
- List-directed input with no <CR> on last record
- From: john
- Re: List-directed input with no <CR> on last record
- From: glen herrmannsfeldt
- Re: List-directed input with no <CR> on last record
- From: tholen
- Re: List-directed input with no <CR> on last record
- From: Richard E Maine
- Re: List-directed input with no <CR> on last record
- From: glen herrmannsfeldt
- List-directed input with no <CR> on last record
- Prev by Date: Re: List-directed input with no <CR> on last record
- Next by Date: linking c and fortran with pathscale compilers?
- Previous by thread: Re: List-directed input with no <CR> on last record
- Next by thread: Re: List-directed input with no <CR> on last record
- Index(es):
Relevant Pages
|
Loading