Hi Karl,
Thanks for looking into this, and giving an explanation, a historic
perspective...
I certainly think in the past there could have been a stupid compiler
that limited string length, but I am pretty sure it would have died of
old age by now... ;=))
Yes, changing main.c line 591 to 'fp = fopen(cfgfil, "wb");` - ie use
binary mode - would do the trick... but...
But then there is line 618 'int fh = creat(configFile, MODE_private);`
to consider, but since this is for unix, maybe no problem...
The 0x0d comes from lang\ebrc-* files, in Windows. The remote git
repository would only use 0x0a, but depending on your git config, when
you clone/pull, line endings are converted to native 0x0d 0x0a... but
that is NOT where this 0x0d comes from...
See tools/buildsourcestring.pl, lines 85 - 89 - regardless of what is in
the input file, which is stripped at line 49 - 51, with 'chomp $line;
$line =~ s/\r*$//;', if the OS is Win type then " 0x0d, 0x0a,"; is
appended to the hexified array...
So if you chose to keep the text mode above, you could remove that if
($OSNAME =~ /Win/) { switch, and ONLY add " 0x0a,", as in unix...
But I am also fairly sure these days you could remove lines 83 - 89,
etc... that is write the lines as is, in inverted commas... not convert
it to a hexified string...
Best regards, Geoff.
