[fpc-devel] FPCUnit: change proposal

2008-04-16 Thread Graeme Geldenhuys
Hi, We use FPCUnit and DUnit2 (branch of DUnit v1) extensively in the tiOPF [http://www.tiopf.com] project. DUnit2 has some impressive enhancements added and improved design. One of the improvements is built-in support of SetupOnce/TeardownOnce without the need for Decorators. Currently we

Re: [fpc-devel] FPCUnit: change proposal

2008-04-16 Thread Michael Van Canneyt
On Wed, 16 Apr 2008, Graeme Geldenhuys wrote: Hi, We use FPCUnit and DUnit2 (branch of DUnit v1) extensively in the tiOPF [http://www.tiopf.com] project. DUnit2 has some impressive enhancements added and improved design. One of the improvements is built-in support of

Re: [fpc-devel] FPCUnit: change proposal

2008-04-16 Thread Graeme Geldenhuys
Michael Van Canneyt wrote: If you leave the decorators intact, I don't see why not. I don't think using one excludes the other ? No, the plan was to leave the decorators as is. Simply add more functionality to the fpcunit.pp file. Regards, - Graeme -

Re: [fpc-devel] MSEide+MSEgui binary package

2008-04-16 Thread Martin Schreiber
On Tuesday 15 April 2008 21.13:41 Jonas Maebe wrote: On 15 Apr 2008, at 21:05, Martin Schreiber wrote: Moving msesysintf from implementation uses to interface uses in msefileutils fixes the issue. I know what causes the crc problem: the fact that msesysintf declares routines as external

Re: [fpc-devel] MSEide+MSEgui binary package

2008-04-16 Thread Marco van de Voort
On Tuesday 15 April 2008 21.13:41 Jonas Maebe wrote: generated because it is possible that units which were compiled after only the interface was parsed may already contain calls to the non- external but regularly mangled Pascal name). You are right, after moving all exernal name

Re: [fpc-devel] MSEide+MSEgui binary package

2008-04-16 Thread Micha Nelissen
Marco van de Voort wrote: You are right, after moving all exernal name declarations to interface I could move back uses msesysintf to implementation in msefileutils and the project compiled. Maybe we should have a known issues entry for this? Perhaps but isn't it quite logical one should

Re: [fpc-devel] Rebuilding fpc-2.3.1.go32v2.zip

2008-04-16 Thread Robert Riebisch
Tomas Hajny wrote: You could have said that, before I fiddled around with slow VMs. ;-( When has this been fixed? IIRC I tried this in January to build FPC 2.2.0 for go32v2 and it didn't work on Windows 2000. I haven't said that anything has been fixed with FPC, just that the DOS I

Re: [fpc-devel] MSEide+MSEgui binary package

2008-04-16 Thread Jonas Maebe
On 16 Apr 2008, at 10:38, Micha Nelissen wrote: Marco van de Voort wrote: You are right, after moving all exernal name declarations to interface I could move back uses msesysintf to implementation in msefileutils and the project compiled. Maybe we should have a known issues entry for this?

Re: [fpc-devel] Rebuilding fpc-2.3.1.go32v2.zip

2008-04-16 Thread Tomas Hajny
On Wed, April 16, 2008 14:25, Robert Riebisch wrote: Tomas Hajny wrote: . . Did you see my example code in the symify.pp broken thread? . . Yes, thanks, I saw it but haven't had time to do something with it yet. Tomas ___ fpc-devel maillist -

Re: [fpc-devel] MSEide+MSEgui binary package

2008-04-16 Thread Tomas Hajny
On Wed, April 16, 2008 10:38, Micha Nelissen wrote: Marco van de Voort wrote: You are right, after moving all exernal name declarations to interface I could move back uses msesysintf to implementation in msefileutils and the project compiled. Maybe we should have a known issues entry for

Re: [fpc-devel] MSEide+MSEgui binary package

2008-04-16 Thread Micha Nelissen
Tomas Hajny wrote: On Wed, April 16, 2008 10:38, Micha Nelissen wrote: Perhaps but isn't it quite logical one should put these in the interface part? How the hell is the compiler otherwise going to know the right name when only parsing the interface? Well, this statement assumes that all

[fpc-devel] Fixes branch contains cleanroom code

2008-04-16 Thread Michael Van Canneyt
Hello, The fixes branch now contains all cleanroom code from trunk, which is now hopefully relatively bugfree. Please test any applications that you are developing using the fixes branch, and report any errors due to this merge as soon as possible. If no grave errors are detected, the release

Re: [fpc-devel] Request to apply patch of bug 0010959

2008-04-16 Thread Luiz Americo Pereira Camara
Tomas Hajny wrote: On Wed, April 16, 2008 03:39, Luiz Americo Pereira Camara wrote: In response to bug report 0010959, i've uploaded a patch to fix the issue, but the reporter closed the bug before the patch was applied. So, i'd like to someone to apply the patch so i can send more

Re: [fpc-devel] Request to apply patch of bug 0010959

2008-04-16 Thread Luiz Americo Pereira Camara
Vincent Snijders wrote: Luiz Americo Pereira Camara schreef: In response to bug report 0010959, i've uploaded a patch to fix the issue, but the reporter closed the bug before the patch was applied. So, i'd like to someone to apply the patch so i can send more improvements to sqlite3ds I

Re: [fpc-devel] symify.pp broken

2008-04-16 Thread Tomas Hajny
On Tue, April 15, 2008 11:21, Robert Riebisch wrote: Tomas Hajny wrote: However, I can't believe that information about this offset (i.e. size of the stub) isn't already available somewhere in the exe file itself (either in the general header or possibly in the COFF section headers), I just