As you probably guess, the issue for the last line " I2:=I1 as IIntf2;" is that
I1 is implemented by "O: TClass1" which no longer supports"IIntf2" - hence the
error "interface not supported".
It would be nice if the class could know it is part of an "implements"
structure and defer to the "paren
Thanks for info.
Well. Now I see the technical reason for it.
I thought so too.
Sure, I'm not a guru in compiler construction, but I'd like to know.
Is this a logic by design that I easily get into a situation when querying
interfaces is not "transitive".
I mean, having one of class interfaces I
Hi again
Original-Nachricht
> Datum: Wed, 25 Nov 2009 17:11:27 +0100
> Von: Peter Beisel
> An: FPC-Pascal users discussions
> Betreff: Re: [fpc-pascal] Re: [fpc-devel] cpu
> thank's for the hint. I could now fix unit cpu.pp
> The problem was the calling convention
> (all assam
should be {$calling oldfpccall} instead.
Jonas
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
__ NOD32 4635 (20091125) Information __
Diese E-Mail wurde vom NOD32 antivi
On 25 Nov 2009, at 11:46, Schatzl Thomas wrote:
Hi,
is there anyone who ported cpu.pp (from Thomas Schatzl) to fpc 2.2.4
(target go32v2)
it compiles out of the box with the 2.2.4 go32v2 compiler.
You will want to add a {$CALLING PASCAL} statement at the top of the
units - some assembly
Hi,
> is there anyone who ported cpu.pp (from Thomas Schatzl) to fpc 2.2.4
> (target go32v2)
it compiles out of the box with the 2.2.4 go32v2 compiler.
You will want to add a {$CALLING PASCAL} statement at the top of the units -
some assembly code assumes some (ancient) calling convention.
On Wed, 25 Nov 2009, Jonas Maebe wrote:
On 22 Nov 2009, at 19:02, Jonas Maebe wrote:
On 21 Nov 2009, at 14:20, Michael Van Canneyt wrote:
I have been thinking along similar lines, and made an implementation for
beep
that works with a handler. It's not yet committed, as I was trying to ma
On 22 Nov 2009, at 19:02, Jonas Maebe wrote:
On 21 Nov 2009, at 14:20, Michael Van Canneyt wrote:
I have been thinking along similar lines, and made an
implementation for beep
that works with a handler. It's not yet committed, as I was trying
to make an
LCL plugin which would work on Lin
