Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Thaddy
On 12-11-2010 13:07, Marco van de Voort wrote: In our previous episode, Thaddy said: Marco, there has been a Bhoem GC for delphi on my website for many years Please add it to the wiki, together with whatever experiences you have with it. ___ fpc-d

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Joost van der Sluis
On Fri, 2010-11-12 at 09:51 +0200, Graeme Geldenhuys wrote: > Op 2010-11-11 15:31, Michael Van Canneyt het geskryf: > > If guarantees are needed: > > Meanwhile, one can buy a support contract from > > http://www.lazarussupport.com/. > > A applaud them for starting that, but that business is only

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread DaWorm
Rather than filling up the list with why this particular issue (something I've never done, and don't care about) behaves differently than Delphi, could someone instead focus on how to perform the needed task(s) with FPC? FPC doesn't work the way Delphi does. Take that as a given. Then figure out

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Thomas Schatzl
Hi, On Fri, 12 Nov 2010 12:26:38 +0100 (CET), Dimitri Smits wrote: > - "Thomas Schatzl" schreef: >> Imo: Jonas already stated, the time of the release for interfaces is >> not >> guaranteed - afaik the docs/specs only state that they "will be >> released if >> the reference count gets zero"

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Florian Klaempfl
Am 12.11.2010 08:51, schrieb Graeme Geldenhuys: > > Creating developer tools has another problem of it's own. Unlike Delphi, > there is no stable, long term shipment of compiled units and specific FPC > version, so in the world of FPC, developers tools must ship as source code. > This again raise

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Marco van de Voort
In our previous episode, Thaddy said: > Marco, there has been a Bhoem GC for delphi on my website for many years Please add it to the wiki, together with whatever experiences you have with it. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Thaddy
Marco, there has been a Bhoem GC for delphi on my website for many years ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Dimitri Smits
- "Thomas Schatzl" schreef: > Hi, > > On Fri, 12 Nov 2010 00:46:43 +0100 (CET), Dimitri Smits > wrote: > > > > it seems that the stackvariables are NOT unloaded in the correct > order > > (ie: reverse order of declaration). > > It shouldn't matter in what order you fill them, but in the o

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Marco van de Voort
In our previous episode, Thomas Schatzl said: > What would be interesting would be how garbage-collected Delphis handle > this, can anyone help? Other than that, there is imo nothing else to say > than that Pascal/Delphi(*) does not have explicitly scoped lifetimes with > automatic destructor call

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Marco van de Voort
In our previous episode, Graeme Geldenhuys said: > Creating developer tools has another problem of it's own. Unlike Delphi, > there is no stable, long term shipment of compiled units and specific FPC > version, so in the world of FPC, developers tools must ship as source code. > This again raise th

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Thomas Schatzl
Hi, On Fri, 12 Nov 2010 00:46:43 +0100 (CET), Dimitri Smits wrote: > > it seems that the stackvariables are NOT unloaded in the correct order > (ie: reverse order of declaration). > It shouldn't matter in what order you fill them, but in the order they are > declared. (like good practice in cons

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Graeme Geldenhuys
Op 2010-11-11 15:31, Michael Van Canneyt het geskryf: > If guarantees are needed: > Meanwhile, one can buy a support contract from http://www.lazarussupport.com/. A applaud them for starting that, but that business is only related to Lazarus development as far as I understand, it does not touch/af

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Marc Weustink
Dimitri Smits wrote: ok, answering my own mail after a small test below - "Dimitri Smits" schreef: what I DON'T do is use it like in your example, Graeme. I always assign the result to a local variable, which goes out of scope in an implicit finally block at method-exit. Haven't tried if

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-12 Thread Dimitri Smits
ok, answering my own mail after a small test below - "Dimitri Smits" schreef: > what I DON'T do is use it like in your example, Graeme. I always > assign the result to a local variable, which goes out of scope in an > implicit finally block at method-exit. Haven't tried if this does > (not)

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-11 Thread Michael Van Canneyt
On Thu, 11 Nov 2010, Graeme Geldenhuys wrote: Op 2010-11-11 01:21, Henry Vermaak het geskryf: Why didn't they just set a bounty or pay a compiler dev to fix it? Because that is still no guarantee that it will be implemented in a timely fashion. Our company tried that route before without s

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-11 Thread Dimitri Smits
- "Graeme Geldenhuys" schreef: > Hi, > > Attached is a simple console application that outputs a hierarchy of > log > information. Under Delphi 7 we used to use a TInterfacedObject > descendant > to track the call stack. This same trick was very handy for changing > and > restoring the mous

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-11 Thread Alexander Klenin
On Thu, Nov 11, 2010 at 21:43, Henry Vermaak wrote: > On 11/11/10 10:18, Jonas Maebe wrote: >>> Why didn't they just set a bounty or pay a compiler dev to fix it? >>> I'm sure that would be cheaper than buying lots of Delphi licences. >> >> I don't think that this is something that can simply be f

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-11 Thread Thaddy
On 11-11-2010 0:21, Henry Vermaak wrote: On 10 November 2010 18:13, Alexander Klenin wrote: Why didn't they just set a bounty or pay a compiler dev to fix it? I'm sure that would be cheaper than buying lots of Delphi licences. Henry ___ It isn't! Not

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-11 Thread Graeme Geldenhuys
Op 2010-11-11 01:21, Henry Vermaak het geskryf: > > Why didn't they just set a bounty or pay a compiler dev to fix it? Because that is still no guarantee that it will be implemented in a timely fashion. Our company tried that route before without success. We set a $500 bounty, it was accepted ver

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-11 Thread Henry Vermaak
On 11/11/10 10:18, Jonas Maebe wrote: On 11 Nov 2010, at 00:21, Henry Vermaak wrote: On 10 November 2010 18:13, Alexander Klenin wrote: As a piece of anecdotal evidence, the fact that FPC does not "properly" support interfaces was the reason for at least one company I worked for to reject it

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-11 Thread Jonas Maebe
On 11 Nov 2010, at 00:21, Henry Vermaak wrote: > On 10 November 2010 18:13, Alexander Klenin wrote: >> As a piece of anecdotal evidence, the fact that FPC >> does not "properly" support interfaces was the reason >> for at least one company I worked for to reject it and move to Delphi >> 2007 ins

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-11 Thread Henry Vermaak
On 10 November 2010 18:13, Alexander Klenin wrote: > As a piece of anecdotal evidence, the fact that FPC > does not "properly" support interfaces was the reason > for at least one company I worked for to reject it and move to Delphi > 2007 instead > (from Delphi 7). Why didn't they just set a bou

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Michael Van Canneyt
On Wed, 10 Nov 2010, Dimitrios Chr. Ioannidis wrote: Στις 10/11/2010 3:01 μμ, ο/η Michael Van Canneyt έγραψε: On Wed, 10 Nov 2010, Martin Schreiber wrote: On Wednesday, 10. November 2010 11.24:52 Michael Van Canneyt wrote: Nowhere is the Delphi behaviour guaranteed, not even by Delphi.

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Michael Van Canneyt
On Thu, 11 Nov 2010, Alexander Klenin wrote: As a piece of anecdotal evidence, the fact that FPC does not "properly" support interfaces was the reason for at least one company I worked for to reject it and move to Delphi 2007 instead (from Delphi 7). I think that at that time there were more

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Alexander Klenin
As a piece of anecdotal evidence, the fact that FPC does not "properly" support interfaces was the reason for at least one company I worked for to reject it and move to Delphi 2007 instead (from Delphi 7). I can understand the reluctance to implement under-specified behavior, but I think FPC would

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Dimitrios Chr. Ioannidis
Στις 10/11/2010 3:01 μμ, ο/η Michael Van Canneyt έγραψε: On Wed, 10 Nov 2010, Martin Schreiber wrote: On Wednesday, 10. November 2010 11.24:52 Michael Van Canneyt wrote: Nowhere is the Delphi behaviour guaranteed, not even by Delphi. Well, I can always argue that FPC tries to clone/mimic

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Op 2010-11-10 14:32, Marco van de Voort het geskryf: > traceback routines based on TD32 debug info Does this mean we have to > emulate Borland internal debug info to the byte? That's not what I asked. > Trying to guarantee these kind of > implemenation details could bring you into problems on ot

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Op 2010-11-10 11:42, Florian Klaempfl het geskryf: > LogMethod call generates a temp. interface variable for the result. FPC > finalizes this temp. interface immediatly after the call because the > result is not used. Delphi does this apparently delayed. Correct, and that is how the developers of

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Martin Schreiber
On Wednesday, 10. November 2010 11.24:52 Michael Van Canneyt wrote: > > >> Nowhere is the Delphi behaviour guaranteed, not even by Delphi. > > > > Well, I can always argue that FPC tries to clone/mimic Delphi behaviour > > in many ways... it's that little FPC design goal called "delphi > > compatib

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Jonas Maebe
On 10 Nov 2010, at 11:42, Graeme Geldenhuys wrote: I so hope Embarcadero lives up to the developer expectations when it releases cross-platform support. If it does, I'll be the first person to leave Free Pascal behind. And this sort of flame bait is also not useful. Posts in this thread a

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Henry Vermaak
On 10 November 2010 10:26, Graeme Geldenhuys wrote: > > Well, I can always argue that FPC tries to clone/mimic Delphi behaviour in > many ways... it's that little FPC design goal called "delphi > compatibility". Think of all the poor developers trying to port their > Delphi code to FPC.  ;-) If y

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Op 2010-11-10 12:24, Michael Van Canneyt het geskryf: > > Yes, valid and documented code is supported. > This is invalid code which just so happens to work. > > There are more cases where we are incompatible. All of them for good reason. I'm still searching the archives. Mind you tell me what w

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Michael Van Canneyt
On Wed, 10 Nov 2010, Martin Schreiber wrote: On Wednesday, 10. November 2010 11.24:52 Michael Van Canneyt wrote: Nowhere is the Delphi behaviour guaranteed, not even by Delphi. Well, I can always argue that FPC tries to clone/mimic Delphi behaviour in many ways... it's that little FPC des

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Florian Klaempfl
Am 10.11.2010 12:09, schrieb Martin Schreiber: > On Wednesday, 10. November 2010 11.24:52 Michael Van Canneyt wrote: >> Nowhere is the Delphi behaviour guaranteed, not even by Delphi. >>> >>> Well, I can always argue that FPC tries to clone/mimic Delphi behaviour >>> in many ways... it's that

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Marco van de Voort
In our previous episode, Graeme Geldenhuys said: > > Yes, valid and documented code is supported. > > This is invalid code which just so happens to work. > > > > There are more cases where we are incompatible. All of them for good reason. > > I'm still searching the archives. Mind you tell me wh

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Op 2010-11-10 12:24, Micha Nelissen het geskryf: > instruction by assembly instruction? That's what you're talking about > it's not language compatibility, but performance compatibility. I'm not sure where you got the "performance compatibility" from? I did not once mention "performance" in any o

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Michael Van Canneyt
On Wed, 10 Nov 2010, Graeme Geldenhuys wrote: Op 2010-11-10 11:56, Michael Van Canneyt het geskryf: Well, the original coders made assumptions which they're not supposed to make. To be fair, it has worked for over a decade already. Plus many IDE and Compiler add-on vendors implement their

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Op 2010-11-10 11:56, Michael Van Canneyt het geskryf: > > Well, the original coders made assumptions which they're not supposed to make. To be fair, it has worked for over a decade already. Plus many IDE and Compiler add-on vendors implement their products based on Delphi behaviour (even though i

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Op 2010-11-10 12:32, Micha Nelissen het geskryf: > > Because you're a brainless moron. I so hope Embarcadero lives up to the developer expectations when it releases cross-platform support. If it does, I'll be the first person to leave Free Pascal behind. Regards, - Graeme - -- fpGUI Toolki

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Op 2010-11-10 12:32, Micha Nelissen het geskryf: > > Because you're a brainless moron. Oh, that was quick! An instant drop to the name calling level. As usual, I can never have a constructive discussion in this mailing list. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolki

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Op 2010-11-10 11:31, Graeme Geldenhuys het geskryf: > to recreated a product similar to Raize Components's CodeSite product. > http://www.raize.com/DevTools/CodeSite/Default.asp Here is CodeSiteEx's explanation for why it works under Delphi. http://www.ackerson.us/AckersonSoftware/Dev/C

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Michael Van Canneyt
On Wed, 10 Nov 2010, Graeme Geldenhuys wrote: Hi, Attached is a simple console application that outputs a hierarchy of log information. Under Delphi 7 we used to use a TInterfacedObject descendant to track the call stack. This same trick was very handy for changing and restoring the mouse cur

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Micha Nelissen
Graeme Geldenhuys wrote: same application behaviour and outcome, using the same source code. That's got nothing to do with performance as far as I'm concerned. Because you're a brainless moron. Micha ___ fpc-devel maillist - fpc-devel@lists.freepas

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Micha Nelissen
Graeme Geldenhuys wrote: a "managed code" environment with garbage collection. So I guess most developers would expect common "out of scope" rules apply. When a local variable is defined and you leave that method/procedure, it's out of scope. *picky mode* exactly this is true for FPC as well. B

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Jonas Maebe
On 10 Nov 2010, at 11:40, Graeme Geldenhuys wrote: I'm still searching the archives. mail-archive.com is currently not responding for me, but the thread is here: http://www.mail-archive.com/fpc-devel@lists.freepascal.org/msg11126.html (it will probably come back online later today). The

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Jonas Maebe
On 10 Nov 2010, at 11:32, Micha Nelissen wrote: Graeme Geldenhuys wrote: same application behaviour and outcome, using the same source code. That's got nothing to do with performance as far as I'm concerned. Because you're a [snip] That sort of remarks are not welcome on the FPC lists. I

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Florian Klaempfl
Am 10.11.2010 10:42, schrieb Graeme Geldenhuys: > Op 2010-11-10 11:30, Michael Van Canneyt het geskryf: >> >> It depends. You're not supposed to make assumptions on when an interface >> goes out of scope. > > I'll search the mailing list archives for those explanations, thanks. I > don't immediate

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Op 2010-11-10 11:30, Michael Van Canneyt het geskryf: > > It depends. You're not supposed to make assumptions on when an interface > goes out of scope. I'll search the mailing list archives for those explanations, thanks. I don't immediately understand why this is a problem, because the RTL is no

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Michael Van Canneyt
On Wed, 10 Nov 2010, Graeme Geldenhuys wrote: Op 2010-11-10 11:30, Michael Van Canneyt het geskryf: It depends. You're not supposed to make assumptions on when an interface goes out of scope. I'll search the mailing list archives for those explanations, thanks. I don't immediately understa

Re: [fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Micha Nelissen
Graeme Geldenhuys wrote: am saying is that in the current "released" Delphi versions (at least down to D7, probably D6 too) this feature works. The "mouse cursor" trick using the same Interface behaviour has been in tiOPF code for years, and I think that's where I saw it first. Should FPC be co

[fpc-devel] Interface scope incompatibility with Delphi

2010-11-10 Thread Graeme Geldenhuys
Hi, Attached is a simple console application that outputs a hierarchy of log information. Under Delphi 7 we used to use a TInterfacedObject descendant to track the call stack. This same trick was very handy for changing and restoring the mouse cursor too. When you create an instance it logs entry