We may add some sort of special markup in source to
pass that information to hbextern tool, like:
FUNCTION SOMETHING /* @hbextern@ ifdef:HB_COMPAT_C53 */
This can solve other extra requirements, like HB_REQUEST_SCALAR
support, which otherwise cannot be extracted from source.
The mingw approach cannot be easily implemented to support
all compilers, plus it needs to be done after creating
all libs, creating hbextern but before creating the rest
of tools (noteably hbrun). So it's tricky.
Brgds,
Viktor
On 2009.06.23., at 13:32, Przemyslaw Czerpak wrote:
On Tue, 23 Jun 2009, Szak�ts Viktor wrote:
Hi,
Very nice job April.
I was wondering what would it take to generate a *full*
equivalent to include/hbextern.ch.
Few issues which need to be solved to achieve that:
- Add HB_CODEPAGE_* symbols (from source/codepage/*.c)
- Add HB_LANG_* symbols (from source/lang/*.c)
- Honor #if protections to keep source and hbextern.ch
in sync with each other.
- Deleted FM_STAT, FM_NOSTAT (do we need these anyway?)
- Some classes are not picked, like XPP_TBROWSE.
- Some wrong picks like WORKS in getsys.prg.
(maybe some more)
If this would be in place, generation of hbextern.ch could be
made completely automatic, which would be a great step
for easier maintenance, and also to avoid getting the file
unsynced with actual sources.
Without #define preprocessing it's hard to create real list
of functions. It's much easier to create it from final binaries, f.e.
in MinGW build by:
nm harbour-20.dll|grep " T _HB_FUN_" | cut -c20- > func.lst
best regards,
Przemek
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
