[lazarus] The use of FPC and Lazarus for simulation software

[Marco van de Voort]

> On Sat, 20 Sep 2003 12:02:59 +0200 (CEST)
> Michael.VanCanneyt at Wisa.be wrote:

> > On Fri, 19 Sep 2003, P. van der Velde wrote:
> > 
> > > Finally I would like to know if the the DUnit testing system
> > > (http://www.dunit.sourceforge.net) works with FPC and Lazarus? I
> > > have been using this system to test my classes for some time now I
> > > have found that it is one of the best testing systems. It has helped
> > > me remove loads of bugs from my source code.
> > 
> > If it works, only with 1.1, because it makes heavy use of interfaces.
> > 

> Last year I took the code of dunit (version 5.02, I think) and
> changed it so that the testframework unit and the texttestrunner

File testframework.pas not changed so no update needed.
bash-2.05b# ppc386 testframework.pas  -Sd
Free Pascal Compiler version 1.1 [2003/09/20] for i386
Copyright (c) 1993-2002 by Florian Klaempfl
Target OS: FreeBSD/ELF for i386
Compiling testframework.pas
testframework.pas(62,19) Error: No matching implementation for interface method "ITest.Run:TTestResult" found
testframework.pas(63,19) Error: No matching implementation for interface method "ITest.LoadConfiguration(const AnsiString,const Boolean)" found
testframework.pas(63,19) Error: No matching implementation for interface method "ITest.SaveConfiguration(const AnsiString,const Boolean)" found
testframework.pas(63,19) Error: No matching implementation for interface method "ITest.LoadConfiguration(const AnsiString,const Boolean)" found
testframework.pas(63,19) Error: No matching implementation for interface method "ITest.SaveConfiguration(const AnsiString,const Boolean)" found
testframework.pas(460,40) Error: Procedure directive "ASSEMBLER" not allowed in interface section
testframework.pas(473,1) Fatal: There were 6 errors compiling module, stopping
bash-2.05b# 

> Last week I give a try to make the guitestrunner compile and run.
> I had the following problems:
> - AFAIK, Actions are not fully implemented in the LCL.
> - I ran into a compiling problem, I had no solution for: 
>  Error: Symbol can't be published, can be only a class"
> The only reference on the mailinglist told it was possibly a compiler
> bug and that you should retry with fpc 1.1. Unfortunately 1.1 is not
> stable enough this week, due to the reorganization of the linux, unix
> and unixbase units.

This is  starting to work again, rtl-compiler-basepackages-fcl works,
however there are still some makefiles to update.

I could import the current version of dunit into the contrib part of CVS?

It is one of the pkgs on my list (the ones that I use for delphi compability
testing from time to time)