Thanks a lot, Mattias. I had to struggle a bit with widgetsets because
each one had some problems. I'm on Linux, and at the end the Qt WS (i.e.
Qt4) is the only one with gives an acceptable result, with the only
problem of a little memory leakage I've not been able to get rid of. But
finally I
Bart wrote:
> > Q1: do we have some documentation about this overload selection process?
> > Q2: if not, then is the observed behaviour of current fpc by design or
> > undefined?
Depending on the mode @variable can return an untyped pointer
(@my_integer is type Pointer) or a typed pointer (@my_int
On Tue, Feb 25, 2025 at 10:35 PM Tomas Hajny via fpc-devel
wrote:
> No, it's because you used a different compilation mode _and_ FPC treats
> @ differently depending on the compilation mode. If you change "{$mode
> fpc}" to "{$mode delphi}" I guess that Delphi 7 might give you the
> same
> res
On 2025-02-25 20:04, Bart via fpc-devel wrote:
Hi Bart,
I possibly did not search hard enough, but did not find what the
"rules" are regarding overload selection (is that the correct term?).
Consider this simple example:
===
program test;
{$ifdef fpc}
{$mode fpc}
{$endif fpc}
{$apptype conso
Hi,
I possibly did not search hard enough, but did not find what the
"rules" are regarding overload selection (is that the correct term?).
Consider this simple example:
===
program test;
{$ifdef fpc}
{$mode fpc}
{$endif fpc}
{$apptype console}
{$ifndef fpc}
type
TProcedure = procedure;
{$endif
