Hi,
Attached is a patch for fpcUnit, which adds test timing results to the
test results. Individual timings as well as overall timing.
Patch needs to be applied from the root fpc source directory.
Regards,
- Graeme -
--
There's no place like 127.0.0.1
Index: fcl/fpcunit/fpcunit.pp
Hi,
Attached is my first documentation patch.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Is the paszlib package documented in the fpcdocs?
If not, I'm considering using it as my first try at documenting a unit/package. I haven't been able to find the docs yet, so I'll assume it doesn't exist.
Would I begin by creating a paszlib.xml file in the root of the fpcdocs? or should it go
Op Wed, 20 Sep 2006, schreef Scott Pascoe:
Is the paszlib package documented in the fpcdocs?
If not, I'm considering using it as my first try at documenting a
unit/package. I haven't been able to find the docs yet, so I'll assume it
doesn't exist.
To my knowledge there exists no paszlib
Daniël Mantione wrote:
Op Wed, 20 Sep 2006, schreef Scott Pascoe:
Is the paszlib package documented in the fpcdocs?
If not, I'm considering using it as my first try at documenting a
unit/package. I haven't been able to find the docs yet, so I'll assume it
doesn't exist.
To my
Daniël Mantione schreef:
Op Wed, 20 Sep 2006, schreef Scott Pascoe:
Is the paszlib package documented in the fpcdocs?
If not, I'm considering using it as my first try at documenting a
unit/package. I haven't been able to find the docs yet, so I'll assume it
doesn't exist.
To my knowledge
Ok,
Assuming that the makeskel has been run, then it would probably need to be fleshed out.So, would the proper location for the xml documentation file be in the root of the fpcdoc and should it be named paszlib.xml?
Thank you for the clarification and help,
On 9/20/06, Florian Klaempfl [EMAIL
On Wed, 20 Sep 2006, Scott Pascoe wrote:
Is the paszlib package documented in the fpcdocs?
No, it is not.
If not, I'm considering using it as my first try at documenting a
unit/package. I haven't been able to find the docs yet, so I'll assume it
doesn't exist.
Would I begin by creating
Back with another question...
I've run into an error using makeskel and haven't figured out how to fix it.
running makeskel with all of the .pas files in paszlib generated an unhandled exception.
I've narrowed it down to the zbase.pas file, so a command line of :
makeskel --package=paszlib
Daniël,
Thanks, I did that right after I sent the email and got it to generate. Glad to know I'm thinkingalong the correct lines here.
Before I get too much further, the generated xml file has a comment
!-- unresolved type reference Visibility: default --
element name=zbase
...
Is this
Scott Pascoe wrote:
You know also that there are gui tools to write the docs?
Daniël,
Thanks, I did that right after I sent the email and got it to
generate. Glad to know I'm thinking along the correct lines here.
Before I get too much further, the generated xml file has a comment
On 20/09/06, Florian Klaempfl [EMAIL PROTECTED] wrote:
Scott Pascoe wrote:
You know also that there are gui tools to write the docs?
I was just about to mention that to Scott as well. I made some
improvements to the lazde (documentation editor included with
Lazarus). I am busy working on
Under which category should h2pas bugs be reported?
Mattias
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Mattias Gaertner wrote:
Under which category should h2pas bugs be reported?
Probably the 'these-will-only-be-solved-if-you-also-provide-a-patch'
category :-).
Micha
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
On Wed, 20 Sep 2006 22:22:39 +0200
Micha Nelissen [EMAIL PROTECTED] wrote:
Mattias Gaertner wrote:
Under which category should h2pas bugs be reported?
Probably the 'these-will-only-be-solved-if-you-also-provide-a-patch'
category :-).
I know, but hope dies last.
Maybe I can raise some
15 matches
Mail list logo
