Op 6/2/2019 om 6:49 PM schreef Martok:
I'm having a problem here in a sequential image processing application that
seems to test a particularly bad operation mode for the RTL heap manager (on
Windows, but I don't think this matters here).
The work load looks like this: load "normal sized" image,
I found a restriction in properties which is a little disappointing. I get
there’s probably some objective of safety but Pascal is a direct memory access
language so I don’t understand why properties have this unique restriction when
I could do the same thing using functions (pointers can’t be d
On 2019-06-03 16:01, Ryan Joseph wrote:
I found a restriction in properties which is a little disappointing. I
get there’s probably some objective of safety but Pascal is a direct
memory access language so I don’t understand why properties have this
unique restriction when I could do the same thi
Ryan Joseph schrieb am Mo., 3. Juni 2019,
16:36:
> I found a restriction in properties which is a little disappointing. I get
> there’s probably some objective of safety but Pascal is a direct memory
> access language so I don’t understand why properties have this unique
> restriction when I coul
Is the following a bug in the compiler or a feature? Is would seem using
{$mode delphi} allows code which clearly violates range bound to compile
without error.
program Project1;
{$mode delphi}
type
TSuit = (suHeart, suDiamond, suClub, suSpade);
TRedSuit = suHeart..suDiamond;
var
Suit: TR
On Mon, Jun 3, 2019 at 4:46 PM Anthony Walter wrote:
>
> Is the following a bug in the compiler or a feature? Is would seem using
> {$mode delphi} allows code which clearly violates range bound to compile
> without error.
>
> program Project1;
>
> {$mode delphi}
>
> type
> TSuit = (suHeart, su
That fixes it, but then the question is why does {$mode delphi} differ from
{$mode objfpc}?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Anthony Walter schrieb am Di., 4. Juni 2019, 03:27:
> That fixes it, but then the question is why does {$mode delphi} differ
> from {$mode objfpc}?
>
Mode ObjFPC is stricter in some cases. While mode Delphi cares for Delphi
compatibility.
Regards,
Sven
__
