Re: D7 Compiler Bug
From: Marco van de Voort (marcov_at_stack.nl)
Date: 10/06/04
- Next message: Jeremy Collins: "Re: Have you all noticed......"
- Previous message: Tom de Neef: "Re: FloatToStr Reals and whole numbers on XP"
- In reply to: VBDis: "Re: D7 Compiler Bug"
- Next in thread: VBDis: "Re: D7 Compiler Bug"
- Reply: VBDis: "Re: D7 Compiler Bug"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 6 Oct 2004 07:32:11 +0000 (UTC)
On 2004-10-05, VBDis <vbdis@aol.com> wrote:
>>> to take it out.
>>
>>The compiler changed totally from D1 to D2. So they explicitely had to
>>code it into D2. So it is there on purpose.
>
> The documentation says that the Object type is supported for compatibility
> reasons. This might mean that dynamic types (AnsiString...) cannot occur in
> legacy (TP...) code and consequently these new types must not be supported in
> Object.
Yes, that is my opinion (and expectation) too. Even if it was supported, I
only expect it to work when constructed properly. Otherwise it would become
an automatic object.
> But it's a half-hearted policy to support Object even in D7 without
> mentioning or correcting hard limits in the implementation and use of that
> data type. The Delphi compiler IMO is very reliable, so it's very strange
> to learn that there exist situations where the compiler definitely
> produces broken code :-(
IMHO this is a documentation fault, and the compiler is fine. FPC
independantly has the same behaviour.
It's a pity that it hasn't been released to PD (or MPL) yet, but I still
want to try to get Turbo Vision compiling under Delphi one day. That would
really stress the object mechanism.
- Next message: Jeremy Collins: "Re: Have you all noticed......"
- Previous message: Tom de Neef: "Re: FloatToStr Reals and whole numbers on XP"
- In reply to: VBDis: "Re: D7 Compiler Bug"
- Next in thread: VBDis: "Re: D7 Compiler Bug"
- Reply: VBDis: "Re: D7 Compiler Bug"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|