[fpc-devel] FPC 2.4.0rc1 and bug #15206

Sergey Bochkanov shadeofgray at yandex.ru
Mon Dec 7 14:58:05 CET 2009


> Everything compiles fine here on Linux/i386 and Linux/x86_64, although
> with 2.5.1 (I don't have a 2.4.0 available right now for those  

Not sure whether bug was fixed or just made less apparent.

> You may want to compile the compiler with debug info: download the
> sources, go into the fpc directory and type
>    make OPT="-O- -gl" all

I'll try to do it and write about results.

> Our tests are very simple:
> a) their file names have to start with "t" and the extension has to be
> ".pp"
> b) if they require special command line options, they have to be  
> mentioned in the first line of the test program file like this:  
> { %opt=-Mdelphi -Si }
> c) the test programs have to exit with exit code 0 if they were  
> successful, and with a non-zero exit code otherwise

Very   simple  and  pretty  compatible  with  my framework. However, I
have several questions:
0. What about newlines? Unix, Windows, does not matters?
1.  Can  test  files reference another units? Typical test consists of
starter  program,  which  prepares  environment  and  calls  unit test
(separate  unit),  which uses unit being tested (separate unit), which
uses several supplementary units.
2.  Where  should  I  place  these  "another  units"  and how should I
reference them?
3.  I  want  to  test  package  under different compiler optimizations
("/O1",  "/Os",  ...)  Should  I  include  different  combinations  of
parameters into my set of tests - i.e. write test1_o1.pp, test1_o2.pp,
test1_os.pp? Or I have to leave such things for Makefile?

With best regards,
 Sergey                          mailto:shadeofgray at yandex.ru

More information about the fpc-devel mailing list