Hi April,
On 2009.07.13., at 7:30, April White wrote:
hbextern and hbdoc have the same limitation - both read only files
with the OS line endings and only produce output with the OS line
endings.
I've altered hbextern to read CRLF/LF/CR files, and I will work on
hbdoc in a similiar manner.
I put to you these question: for common files such as hbextern.ch
and the text/ascii output of hbdoc,
(1) should the output line endings be consistent across all platforms,
No, for text files Harbour uses native EOLs, which
means to always use the platform specific EOL on
any platform.
That aspect is automatically handled by SVN. It will
automatically handle all kinds of EOLs on upload, and
use the platform specific one on download.
This is ensured by prop 'svn:eol-style native' setting.
For Harbour utilities it's best practice to accept and
handle all kinds of input EOLs automatically (well, at
least CRLF and LF. Pure CR is not used on any Harbour
supported platforms and quite unlikely anyway nowadays).
For output, it's the best to use the platform specific
EOL, which is hb_osNewLine().
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
