> I read the Wiki about this article, it's looks like very complicated for
me. :-(
> Can anybody show me a very simple example?
Well, it surely is not a beginner's topic. Tell me, if I give:
type
TMyThread = class(TThread)
procedure Execute; override;
end;
procedure TMyThread.Execute;
b
On Tue, May 26, 2015 19:30, Serguei TARASSOV wrote:
Hi,
> How is possible to get some debug information at runtime?
> Assuming, the program compiled with required debug information/symbols.
>
> I.e. how to get actual call stack state and called procedures names
> within the procedure or method?
Hi All,
How is possible to get some debug information at runtime?
Assuming, the program compiled with required debug information/symbols.
I.e. how to get actual call stack state and called procedures names
within the procedure or method?
Regards,
Serguei
__
On Tue, May 26, 2015 18:12, Géza Kovacs Géza wrote:
Hi!
> I read the Wiki about this article, it's looks like very complicated for
> me. :-(
> Can anybody show me a very simple example?
> Below is a code, i would like to run it multithread both under Windows
> and Linux.
>
> Program Sorting;
> c
Am 2015-05-26 um 10:27 schrieb Michael Schnell:
As the work that needs to be done by the OS is a lot more than what is done by
the fpc library, I suppose that there is no noticeable difference.
I think that depends on the size of the file(s).
If you copy thousands of files with only a few byte
Hi!
I read the Wiki about this article, it's looks like very complicated for me. :-(
Can anybody show me a very simple example?
Below is a code, i would like to run it multithread both under Windows
and Linux.
Program Sorting;
const
n = 999000;
var
data : array [1..n] of integer;
On 05/25/2015 06:42 AM, Géza Kovacs Géza wrote:
Hi All!
What is the faster and more efficient, using the TFileStream or the
classical way ("file of byte", or "file") type with
blockread/blockwrite and the other well-know procedures?
What is the better, faster on large files?
As the work that ne
Am 26.05.2015 01:20 schrieb "luciano de souza" :
> But, say me: is the problem I faced related to 2.4 version? In newer
> version, would it be possible to use something like I have proposed or
> will the same behviour be maintained?
No, because there is no way for the compiler to know that the typ
