Am 2015-03-10 um 17:40 schrieb Sven Barth:
It mutes the warning with the ID 5089 (the ID can be seen with -vq). So as
long as the managed and unmanaged ones use the same warning ID (AFAIR they do) they
will both be silenced.
Ups, no, they are different. So at least if you use a current 2.7.1
On 3 March 2015 at 17:47, Anthony Walter sys...@gmail.com wrote:
This is a public notice. Get Lazarus has switched from hosting arbitrary
revisions to hosting setup programs from nightly builds.
http://www.getlazarus.org/setup/
Going forward each night the current svn trunk sources of FPC
On 2015-03-12 23:15, Graeme Geldenhuys wrote:
// FPC cross-platform implementation
function CallerAddr: Pointer;
begin
Result := get_caller_addr(get_frame);
end;
I was told from another source my FPC implementation was incorrect and
should rather be:
[Anybody that could explain the
On 2015-03-13 00:03, Graeme Geldenhuys wrote:
Next part is to extract the line info information to confirm that the
addresses I now see are indeed correct.
Success!!! :) Finally I have full details of where a failure occurs.
===
tiOPFUnitTestsFPGui.Non
Hi,
Could somebody confirm if the Delphi ASM does the same as the FPC code?
This code is used in a unit testing framework to help report the exact
location of where an error was raised. It seems to work well in Delphi,
but not in FPC.
Under FPC it seems to always return the same address, even
