[Python-3000] Lines breaking
janssen at parc.com
Fri Jun 1 19:51:17 CEST 2007
> I agree that that looks nice in my editor, but it is not Unicode-
> conforming practice, and I suspect that if you experiment with any
> printer you'll discover that you get an empty line at the top of the
This seems to me to be a non-issue; most "text" files are actually
data files (think about it), and were never intended to be printed.
> I also suspect that any program that currently is used to process
> those files' content by lines probably simply treats the FF as
> whitespace, and throws away empty lines.
Nope. At least, my program doesn't. And I don't think it's an
appropriate assumption, either. Many programs are written to ignore
empty lines in their input, but many, maybe more, are not. Blank
lines convey critical information in many contexts.
> If so, it will still work
> with FF treated as a hard line break in line-processing mode, since
> the trailing NL will now generate a (superfluous) empty line.
Nope. The line-breaking is actually used (and this is common in data
represented as text files) as part of the parsing process, so by
turning it into two lines you've broken the program logic.
More information about the Python-3000