Re: writeln in threads on linux
> Can anyone explain why i get output like this in a small test program:
> Inside Thread
> Main Loop
> Inside Thread
> Main Loop
> Inside Thread
> Main Loop
That's because the line terminator!
#10#13 or #13#10 acts differently
So, check in the source code which one is used, because the first one is
not suitable in Windows!
As you supposedly know, the end line terminator is different on Mac, Unix
and Windows.
Mac only uses #13
Unix only uses #10
Windows uses #13#10 (CRLF)
This comes from the fact that telex machines needed to complete two
different actions in order to start writing in a new line (just like what
you have to do on a normal typewriter): first to step on the next row,
then to put the head at the beginning of the row.
So, basically #10 means Line-Feed (LF) (step to the next row)
While #13 means Carriage Return (CR) which means "move the carriage -the
printing head- to the beginning of the row) - or what you are doing on a
typewriter by hand, using that lever from the right upper part of the
machine.
so, when OS-es split up, the kept what they wanted, although MS had had to
preserve the standard as long as they was part of IBM those times, and IBM
telex machines needed the time of two caracter printing to complete a CRLF
operation.
But I I've seen, sometimes in FP source codes the CRLF is using as LFCR
(Continue reading)
because the ret value is 0 if invalid file / directory passed. ret is > then the passed bufferlen "255" if it needs a larger buffer to store it in or it is between 1 and 255 if a valid value. same error with GetShortName reference http://windowssdk.msdn.microsoft.com/en-us/library/ms685896.aspx http://windowssdk.msdn.microsoft.com/en-us/library/ms685885.aspx --- dale _______________________________________________ fpc-pascal maillist - fpc-pascal@... http://lists.freepascal.org/mailman/listinfo/fpc-pascal
RSS Feed