[fpc-pascal]Classes/Objects/Pointers / Pointer Help

[Lee, John]

ok, so for the appropriate o/s we 

repeat
1 just scan the local disks for eg the ppc386.exes, fp.exes, ppc.cfgs,
base*,zips, ide*.zips or whatever are appropriate for the o/s & o/p to
screen what versions etc the user has on the system  
2 then look in ppc.cfg & check whether the references there eg to paths &
files are valid  
3 generate n programs & compile them, o/p any compile errors  
4 run tests (eg those in the cvs ??? or the ones in the program we are
discussing? or both) & o/p results/errors 
5 if tests are in loop stop the pograms & o/p error message
until (timeout or ctrl/c or ???);  

Sounds as if 3 & 4 are the difficult bits...   

Regards John

-----Original Message-----
From: Anton Tichawa [mailto:anton.tichawa at chello.at]
Sent: Wednesday, February 12, 2003 04:18
To: fpc-pascal at deadlock.et.tudelft.nl
Subject: Re: [fpc-pascal]Classes/Objects/Pointers / Pointer Help


Hello, John!

> can also contribute eg a (non OO) FP test unit? if you like. Any ideas
> about how to define the 'features' to be tested? Regards John

***
procedure define;
begin
  lock;  // (?)
  brainstorm;
  ..
***

well, my first contribution to a brainstorming of features to be tested is -

* DETERMINE SYSTEM STATUS ..: the test program should determine and evaluate

the status of installed compilers / ides on the given system, without write 
operations e. g. to the mass storage media. things such as missing, 
misplaced, misspelled, .., or ambiguos configuration, e. g. in the file 
fpc.cfg, should be mentioned on the screen. upon user intervention - and
also 
timeout is a user intervention - the status should be first saved and then
be 
overloaded with a new one that seems appropriate to both user and tester.
but 
that's not really important at the moment. the important thing is that the 
saved stati - those that didn't seem appropriate at the moment - are the
most 
valuable thing of free pascal from a certain point of view. this is the 
output of the tester program, the bug list, and will help answer any
question 
that may come in the future. i'm talking about, well, excuse my poor english

here, fehler (d) = errrors (e) (?), because in every such "thing" is one bit

of truth that will surely be reconsidered as free pascal development 
continues. no bug must be lost, or so .. uh.

anton tichawa.

----------

"Adas Methode war, wie sich zeigen wird, Tagträume in offenbar korrekte 
Berechnungen einzuweben."

Doris Langley Moore: Ada, Countess of Lovelace (London 1977).

----------

Anton Tichawa
Volkertstrasse 19 / 20
A-1020 Wien
mobil: +43 664 52 07 907
email: anton.tichawa at chello.at

----------
_______________________________________________
fpc-pascal maillist  -  fpc-pascal at lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

This e-mail and any attachment is for authorised use by the intended recipient(s) only.  It may contain proprietary material, confidential information and/or be subject to legal privilege.  It should not be copied, disclosed to, retained or used by, any other party.  If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.  Thank you.