Thank you for the clear explanation.
> On Oct 24, 2021, at 1:05 AM, Michael Van Canneyt via fpc-pascal
> wrote:
>
>
>
> On Sat, 23 Oct 2021, P Padilcdx via fpc-pascal wrote:
>
>> Hello,
>>
>> Was trying to declare a procedure with an array argument, e.g. procedure
>> p(a: array[1..9] of
In the end we have a black box with Indy that isn't going to be opened.. and
from the sound of it, a dated method of manually checking for i/o (in this case
likely with select() and a zero timeout..). Calling that and sleep() over and
over millions of times..
I'm sorry to the OP if I'm assuming
On Sat, 23 Oct 2021, P Padilcdx via fpc-pascal wrote:
Hello,
Was trying to declare a procedure with an array argument, e.g. procedure
p(a: array[1..9] of int64), and the compiler complained as it seems only
accepts open arrays. If I set a type alias for the array, e.g. type t =
array[1..9]
Hello,
Was trying to declare a procedure with an array argument, e.g. procedure p(a:
array[1..9] of int64), and the compiler complained as it seems only accepts
open arrays. If I set a type alias for the array, e.g. type t = array[1..9] of
int64, then I can declare the procedure p(a: t). This
Am 07.10.21 um 19:41 schrieb Bo Berglund via fpc-pascal:
The question is: how to find what is still using CPU?
Have a look at the tool sysprof. This is a statistical sampling profiler
that can show you a call tree with percentages of CPU consumption. Thee
are also other sampling profilers ar
