I have found in xharbour ng this sample for creating a function list
.will be a starting point for doc?
#include "common.ch"
#include 'Inkey.ch'
#include 'fileio.ch'
#include 'hbeol.ch'
static aFuncsName:={}
static cRegExHbFunc
static cRegExFunc
static cRegExClass
static cRegExClassTran
static cR
The harbour minigui project have a documentation ready to use
I think that Can added to Harbour.doc (i can convert in pdf with commercial
tool)
http://hmgs-minigui.cvs.sourceforge.net/*checkout*/hmgs-minigui/minigui/Harbour/doc/%28x%29harbour.chm
Massimo Belgrano
2009/1/14 Viktor Szakáts
> Hi
Hi Mindaugas,
I don't know it very deeply, just stumbled upon it accidentally while
reading about Python 3.0. The end result looks very clean,
just like the doc sources (even cleaner than MediaWiki, if such
comparison makes any sense). So Harbour came instantly in mind.
It doesn't seem like a sour
+1
2009/1/14 Mindaugas Kavaliauskas
>
> Writing a simple source parser (parses documentation tags inside comments),
> it's a few hours job. I think we need one for function documentation.
>
>
>
> Best regards,
> Mindaugas
> ___
> Harbour mailing list
Hi,
http://sphinx.pocoo.org/
- Documentation format
Viktor, can you add some comment about this documentation system. Does
Sphinx parses source files? Can it parse .prg code?
I'm used to see to sources, but sometimes it would be more quick to look
to docs for functio
Here is all my patches, pls test and comment. It's possible some
mistakes crippled in, while applying/merging all these patches.
Also don't forget to check the TOFIX section at the end.
2009-01-14 16:15 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* source/rtl/net.c
* contrib/hbziparc/hbzipa
