On 3 aug 2006, at 19:03, Jonas Maebe wrote:
on't bother with Solaris in 2.0.x, it won't work at all. None of
the Solaris fixes from 2.1.1 have been merged
On a positive note, Sparc/Solaris works fine in 2.1.1
Jonas
___
fpc-pascal maillist - fpc
Looking forward to getting that far :-) I'm considering running up v8 in a
SPARCserver but right now I can do without the extra heat.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_
Hello!
I've recently switched from Delphi to FP and never been exposed to
TP-style objects before.
At first sight they seem very similar to Delphi-style classes. However,
it seems it is possible to allocate them on the stack - very convenient.
Is it right to assume they are automatically de
> Is it right to assume they are automatically deallocated when they go
> out of scope (e.g. no need to free them manually)?
The space of the object is cleaned. However if the object uses dyn memory,
you will have to call the destructor (destroy) to make the object cleanup.
In general it is cons
Marco van de Voort wrote:
The space of the object is cleaned. However if the object uses dyn memory,
you will have to call the destructor (destroy) to make the object cleanup.
In general it is considered a good custom to destroy them.
So no C++-style automatic deallocation (the destructor is
Marco van de Voort wrote:
>> Is it right to assume they are automatically deallocated when they go
>> out of scope (e.g. no need to free them manually)?
>
> The space of the object is cleaned. However if the object uses dyn memory,
> you will have to call the destructor (destroy) to make the obje
> Marco van de Voort wrote:
>
> > The space of the object is cleaned. However if the object uses dyn memory,
> > you will have to call the destructor (destroy) to make the object cleanup.
> >
> > In general it is considered a good custom to destroy them.
>
> So no C++-style automatic deallocatio
