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

Jonas Maebe jonas.maebe at elis.ugent.be
Mon Dec 7 15:14:46 CET 2009

On 07 Dec 2009, at 14:58, Sergey Bochkanov wrote:

> Very   simple  and  pretty  compatible  with  my framework. However, I
> have several questions:
> 0. What about newlines? Unix, Windows, does not matters?

Does not matter, handled by svn (and even if not, by FPC).

> 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?

Units can be placed in the same directory as the test program. You can  
just add the to the uses clause of your program. The name doesn't  
matter (other than that it shouldn't start with a "t"), but by  
convention they start with "u" for our tests. Note that we generally  
don't create separate subdirectories for our tests, they're all  
located in only a few, large directories. See http://svn.freepascal.org/svn/fpc/trunk/tests/ 
. We could add an extra alglib directory there in which all of your  
tests are placed.

> 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,
> t

No, the entire testsuite itself is tested using different parameters.  
See http://www.freepascal.org/testsuite/cgi-bin/testsuite.cgi


More information about the fpc-devel mailing list