32bit on Windows 64-bit uses Wow64.. which has a bit of overhead as an
emulation layer. I believe it's the same one they use for ARM64 too. I can only
guess at how optimally it works performance-wise, but compiling a couple
thousand-liner utils was annoying. You could (at least on the machine I
looks like threadid is assigned to getcurrentthreadid in an initthread()
function in thread.inc.
but: getcurrentthreadid looks to be mapped to a changeable thread manager which
is why that might seem weird in the docs..
--
Alexander Grotewohl
https://dcclost.com
___
"break" is a windows built-in. explains the first attempt.
--
Alexander Grotewohl
https://dcclost.com
From: fpc-devel on behalf of Tomas
Hajny via fpc-devel
Sent: Friday, November 27, 2020 11:16:26 AM
To: FPC developers' list
Cc: Tomas Hajny
Subject: Re: [fpc-
I would probably do something like this:
const
ansi_colors: array[0..7] of char = ('0', '4', '2', '6', '1', '5', '3', '7');
procedure PrintColor(fg, bg: byte; s: string);
var
tmp: string;
begin
tmp:=#27+'[0;3'+ansi_colors[fg]+';4'+ansi_colors[bg]+'m'+s+#27+'[0m';
writeln(tmp);
end;
begin
PrintCo
