Alexander Shishkin schrieb:
You also may refactor your class and define array as a pointer to array
(dont use dynamic array - they are zero initialized) and manage memory
manually ( [Get|Realloc|Free]Mem ).
IMO dynamic arrays are not initialized, at least not in Delphi. Only the
pointer is
Op 24 februari 2012 13:40 heeft Hans-Peter Diettrich
drdiettri...@aol.com het volgende geschreven:
IMO dynamic arrays are not initialized, at least not in Delphi. Only the
pointer is initialized (to Nil).
IMO one should not use IMO when claiming easily verifiable facts, it
should be used when
Vincent Snijders schrieb:
Op 24 februari 2012 13:40 heeft Hans-Peter Diettrich
drdiettri...@aol.com het volgende geschreven:
IMO dynamic arrays are not initialized, at least not in Delphi. Only the
pointer is initialized (to Nil).
IMO one should not use IMO when claiming easily verifiable
Op 24 februari 2012 15:14 heeft Hans-Peter Diettrich
drdiettri...@aol.com het volgende geschreven:
it
should be used when writing down an opinion.
What's wrong with leaving the check to others? As an exercise...
Then you should not write in my opinion, but I think or if I
remember correctly.
Hi,
i just update fpc from fixes_2_6 and now lazarus can't create event
handlers. I tried with a clean fpc checked out tree and even i done the
the same with lazarus tree. Everything was deleted, checked out again
and recompiled. The problem persists.
It's very easy to reproduce. Create a
Hi,
i just update fpc from fixes_2_6 and now lazarus can't create event
handlers. I tried with a clean fpc checked out tree and even i done the
the same with lazarus tree. Everything was deleted, checked out again
and recompiled. The problem persists.
It's very easy to reproduce. Create a
Hi,
32 bit FPC default debug info (I assume STABS) shows the classname and the
function name in gdb stack traces which is very useful to navigate in
inherited calls for example.
64 bit FPC default debug info (I assume DWARF) shows the function names only.
Is it possible to list the classnames
On 24 Feb 2012, at 18:46, Martin Schreiber wrote:
32 bit FPC default debug info (I assume STABS) shows the classname and the
function name in gdb stack traces which is very useful to navigate in
inherited calls for example.
64 bit FPC default debug info (I assume DWARF) shows the function
In light of a recent mail thread on the topic and
http://bugs.freepascal.org/view.php?id=21370
From: rtl\inc\lnfodwrf.pp
function DwarfBackTraceStr(addr : Pointer) : shortstring;
var
...
Success : boolean;
begin
{ reset to prevent infinite recursion if problems inside the code }
Quoting http://www.freepascal.org/docs-html/prog/progsu38.html
the {$INCLUDE} directive inserts a string constant in the source code.
...
LINE
Linenumer on which the directive is found.
How hard would it be for me to modify the FPC preprocessor to
Actually I already found it, and it will be trivial to do.
Would this be useful to anyone else? Should I submit a patch?
Basically I'm adding a LINENUM macro (vs. the existing LINE macro)
which inserts the line number as an numeric rather than a string
constant.
-SG
--
This email is fiction.
On 24.02.2012 22:49, Seth Grover wrote:
Quoting http://www.freepascal.org/docs-html/prog/progsu38.html
the {$INCLUDE} directive inserts a string constant in the source code.
...
LINE
Linenumer on which the directive is found.
How hard would it be
On 24.02.2012 23:13, Seth Grover wrote:
Actually I already found it, and it will be trivial to do.
Would this be useful to anyone else? Should I submit a patch?
Basically I'm adding a LINENUM macro (vs. the existing LINE macro)
which inserts the line number as an numeric rather than a string
I've provided a patch.
http://mantis.freepascal.org/view.php?id=21372
Cheers,
-SG
--
This email is fiction. Any resemblance to actual events
or persons living or dead is purely coincidental.
Seth Grover
On Fri, Feb 24, 2012 at 3:13 PM, Seth Grover sethdgro...@gmail.com wrote:
Actually I
14 matches
Mail list logo
