On 30/10/2018 11:45, Charles Johnson wrote:
...
Yes, _writing_ is a different matter and a decision would have to be made
A file has to be written before it can be read. If Perl writes a file
when running under Linux it will write LF as the line terminator. When
running under Windows it will write CR LF. When reading the file under
Windows, Perl will strip out the CR, so the calling script will not see
it. If a file has been written under Windows and is being read under
Linux the CR characters will not be stripped out, but will be returned
as part of the record.
When reading its tv.cache, radio.cache and download_history files
get_iplayer does not care what the line terminator is because it uses |
as a separator. For the options file it uses the line terminator as a
separator. For some options the presence of a CR does not matter. For
others it causes the option to be garbled.
We had a long discussion about this in March in the thread I linked to,
so I don't want to go over old ground. What I wanted to ask was
1. Has anyone else tried running get_iplayer under the Windows bash shell?
2. Can anyone shed any light on why AtomicParsley hangs when run under
the Windows bash shell?
Best wishes
Richard
_______________________________________________
get_iplayer mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/get_iplayer
