Dean,
As requested. Here goes...
Let me know what you think of Item 1? If you wanted to start with any
of these, Item 1 would be good. :-)
===
Item 1
===
I have an idea on improving the console runner output. Running the
app as show
Graeme Geldenhuys schreef:
Dean,
As requested. Here goes...
Let me know what you think of Item 1? If you wanted to start with any
of these, Item 1 would be good. :-)
===
Item 1
===
I have an idea on improving the console runner outpu
On 09/11/06, Vincent Snijders <[EMAIL PROTECTED]> wrote:
> Number of run tests: 20
> Number of errors:0
> Number of failures: 0
IMHO the 'Number of ...' should be enabled with a new -s (and --summary)
switch
That makes sence, yes.
> Hierarchy view for test listing in XML. The XSLT fil
Hello,
I did a plain install from scratch (the
Lazarus-0.9.20-fpc-2.0.4-20061105-win32.exe) and wanted to rebuild
Lazarus. The rebuild with the preinstalled fpc-2.0.4 stops with an error:
Compiling svn2revisioninc.pas
Linking .\svn2revisioninc.exe
.\svn2revisioninc.o(.data+0x14): In function
Adrian Veith schreef:
Hello,
Next problem:
Because I prefer the fpc2.1.1 compiler i changed the setup to use my
fpc-2.1.1. (current svn snapshot). I did a "make clean all" Everything
builds well, but when i try to start lazarus it throws an exception:
Error reading SplashForm.Left. Unknown pr
First, I would prefer a patch to the fpcunit which makes the unit itself
indenpendend from other stuff (xml) so it can be used in the fpc test suite :)
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinf
On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
First, I would prefer a patch to the fpcunit which makes the unit itself
indenpendend from other stuff (xml) so it can be used in the fpc test suite :)
The xml used is the xmlwriter unit - part of FPC. Is this a problem?
Test output is o
On Thu, 9 Nov 2006, Florian Klaempfl wrote:
> First, I would prefer a patch to the fpcunit which makes the unit itself
> indenpendend from other stuff (xml) so it can be used in the fpc test suite :)
The unit fpcunit is independent of XML ?
The package as a whole is dependent on XML, this is c
On 9 nov 2006, at 11:47, Graeme Geldenhuys wrote:
On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
First, I would prefer a patch to the fpcunit which makes the unit
itself
indenpendend from other stuff (xml) so it can be used in the fpc
test suite :)
The xml used is the xmlwriter
On 09/11/06, Jonas Maebe <[EMAIL PROTECTED]> wrote:
> The xml used is the xmlwriter unit - part of FPC. Is this a problem?
The problem is that the xml stuff must be built before you can run
the testsuite with fpcunit tests included (since the fpcunit package
depends on the xml stuff). This mean
On 9 nov 2006, at 12:49, Graeme Geldenhuys wrote:
Ok, so if the OutputFactory idea is also not going to work. Why not
try something completely different. What if every test suite compiled
to a .dll or .so file - nothing more. The fpcUnit executable compiled
previously with a stable compiler a
On Thu, 9 Nov 2006, Jonas Maebe wrote:
>
> On 9 nov 2006, at 11:47, Graeme Geldenhuys wrote:
>
> >On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
> > >First, I would prefer a patch to the fpcunit which makes the unit itself
> > >indenpendend from other stuff (xml) so it can be used in
>> On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
>>> First, I would prefer a patch to the fpcunit which makes the unit
>>> itself
>>> indenpendend from other stuff (xml) so it can be used in the fpc
>>> test suite :)
>>
>> The xml used is the xmlwriter unit - part of FPC. Is this a prob
On 09/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Wait a minute But you need a stable enough compiler to compile the
testsuite right?
That's what I wast trying to get at... You need a compiler already.
As to the order of how things are compiler and tested (RTL, FCL, etc)
I have no i
On Thu, 9 Nov 2006, [EMAIL PROTECTED] wrote:
> >> On 09/11/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
> >>> First, I would prefer a patch to the fpcunit which makes the unit
> >>> itself
> >>> indenpendend from other stuff (xml) so it can be used in the fpc
> >>> test suite :)
> >>
> >> The
On 9 nov 2006, at 13:33, [EMAIL PROTECTED] wrote:
Wait a minute But you need a stable enough compiler to compile the
testsuite right?
You need a lot more compiler functionality to compile the fcl than to
compile individual tests (not to mention that a problem which occurs
when compili
Begin forwarded message:
From: Dean Zobec <[EMAIL PROTECTED]>
Date: 9 november 2006 19:45:56 GMT+01:00
To: Florian Klaempfl <[EMAIL PROTECTED]>, Michael Van Canneyt
<[EMAIL PROTECTED]>
Cc: Graeme Geldenhuys <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: [fpc-pascal] fpcUnit todo list
Jonas Maebe schrieb:
The easiest thing to do is to include fpcunit itself in fcl/inc.
All the units around it can be done in fcl/fpcunit, which is built at
a later stage.
Michael.
I agree with this.
This arises a fundamental question: should the tests for all package
(non rtl/compiler!)
On Thu, 9 Nov 2006, Florian Klaempfl wrote:
> Jonas Maebe schrieb:
> > > > The easiest thing to do is to include fpcunit itself in fcl/inc.
> > >
> > > > All the units around it can be done in fcl/fpcunit, which is built at
> > > > a later stage.
> > > >
> > > > Michael.
> > > I agree with this
Begin forwarded message:
From: Dean Zobec <[EMAIL PROTECTED]>
Date: Fri 10 Nov 2006 00:04:44 GMT+01:00
To: Florian Klaempfl <[EMAIL PROTECTED]>, Michael Van Canneyt
<[EMAIL PROTECTED]>, Jonas Maebe <[EMAIL PROTECTED]>
Subject: Re: Fwd: [fpc-pascal] fpcUnit todo list
Michael Van Canneyt ha s
Hi,
I have to translate a lot of assignements like this:
particle_t = record
name: array [0..Pred(16)] of char;
longi: integer;
pressure: float;
temperature: double;
lati: integer;
end;
ibuf: array [0..Pr
> particle_t = record
> name: array [0..Pred(16)] of char;
> longi: integer;
> pressure: float;
> temperature: double;
> lati: integer;
> end;
>
> ibuf: array [0..Pred(2)] of particle_t;
> (* raw translation by automatic t
22 matches
Mail list logo
