A documentation is important also without documenting HB_STATIC_FUNC
for
now
What do you think about using a robodoc for extract from source
Also here you see that separing prg and c will be more useful for
generating documentation
Yes. Same goes for every tool which makes a decision
about the content based on the extension (or file type).
And even if the tool allows for manual file-type override,
files with mixed types are still practically impossible
to be properly handled.
Is not possible a way of join prg and c file if have same name or
similar whit a fixed extension?
Mysample.prg and Mysample_linked.c will be part of same module during
linking?
I used to use (but not very strictly) this method, f.e.:
w32_reg.prg
w32_regc.c
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
