Hi,
fpc allows to declare a method with the destructor keyword, that is
not a real destructor, because it does not free the memory. For what is
this feature good for?
For example:
Type
TClassA = class
public
destructor Foo;
end;
destructor TClassA.Foo;
begin
end;
var
o: TClass;
begin
2017-01-24 12:48 GMT+01:00 Mattias Gaertner :
> fpc allows to declare a method with the destructor keyword, that is
> not a real destructor, because it does not free the memory. For what is
> this feature good for?
>
with trunk works as expected (Foo does call FreeInstance).
--
Best regards,
Ma
On Tue, 24 Jan 2017 15:33:30 +0100
Maciej Izak wrote:
> 2017-01-24 12:48 GMT+01:00 Mattias Gaertner :
>
> > fpc allows to declare a method with the destructor keyword, that is
> > not a real destructor, because it does not free the memory. For what is
> > this feature good for?
> >
>
> with t
On 1/23/17, Rolf Grunsky wrote:
> I keep ending up with these very long file names which then I can not
> access.
Been there.
I once created a folder and file using W API and \?\\ syntax for
testing purposes.
This all went well, but Windows did not like it and would not let me
remove the file an
On 23/01/17 10:17, Terry Mead wrote:
When compiled and run under Windows it generates the stack trace:
Runtime error 200 at $00401404
$00401404 TEST1, line 6 of test.pas
$00401428 TEST2, line 11 of test.pas
$00401451 main, line 16 of test.pas
$004077D1
Which is what you would expec
Jonas - -O- option didn't do any different but I did bite the bullet and
upgrade to 3.0 which does solve the problem.
Thanks.
On 25/01/2017 6:54 AM, Jonas Maebe wrote:
On 23/01/17 10:17, Terry Mead wrote:
When compiled and run under Windows it generates the stack trace:
Runtime error 200 at $
