On 31 Jan 2020 at 06:53p, August Abolins pondered and said...
 
 AA> Yes.. even viewing text files generated in a unix environment can
 AA> display differently in a DOS environment because of the way end of lines
 AA> are designated.  Could that be a problem when passing around the
 AA> DOS-created NL segments to unix-based systems?

Unix imposes no particular requirement on files with respect to line
endings.  The "standard" of a single newline character terminating a
line is a convention; it doesn't need to be followed.

Indeed, Unix doesn't care what is a file.  As far as the operating
system is concerned, it's just a collection of bytes.

One could easily write a program that would process segments of text
using any line ending one cares to employ, whether '\n', '\r', '\r\n'
or '\n\r'.  Getting this right is a Simple Matter of Programming(TM).

Now, that said, the convention used on Unix makes sense: lines are a
logical thing, their physical presentation on an output device like
a terminal or graphical display is independent of their representation
in the filesystem.  DOS conflates these things by using '\r\n' as a
line-end convention.

 AA> Dan Cross made a fine point about glob expansions.  DOS/Win and unix
 AA> environments just do things differently.

Thank you!

--- Mystic BBS v1.12 A44 2020/01/29 (Windows/32)