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.

Brgds,
Viktor

On Tue, Jun 23, 2009 at 2:43 AM, <ap...@users.sourceforge.net> wrote:

> Revision: 11491
>
> http://harbour-project.svn.sourceforge.net/harbour-project/?rev=11491&view=rev
> Author:   april
> Date:     2009-06-23 00:43:43 +0000 (Tue, 23 Jun 2009)
>
> Log Message:
> -----------
> 2009-06-22 20:38 UTC+0600 April White (april users.sourceforge.net)
>  * examples/hbextern/hbextern.prg
>    * significant re-implementation
>      ; with no params will work like original version
>      ; processes source files with LF terminators
>      ; params to control: recursion, include 'conditions',
>        include classes, include class methods/etc
>      ; execute with -? or --help
>
> Modified Paths:
> --------------
>    trunk/harbour/ChangeLog
>    trunk/harbour/examples/hbextern/hbextern.prg
>
>
> This was sent by the SourceForge.net collaborative development platform,
> the world's largest Open Source development site.
> _______________________________________________
> 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

Reply via email to