Hi Viktor,
Il 26/10/2008 23.33, Szakáts Viktor ha scritto:
Hi folks,
As a rule of thumb xhb functions need to stay
in xhb lib, and other libs should never depend
on xhb lib. Replicating xhb functions in other
libs also don't look like a very good idea, as
this just leads to mutual exclusion of those libs,
unless the function names are made unique. In
this case though it's best if the new functions
also add something to the xhb originals.
I honestly can't say if anything of the above
applies to hbdbgfx, but maybe they would fit
better in hbmisc, rather than living as a separate
lib. hbmisc could be renamed to hbtools to better
reflect the purpose and gather everything useful
but not fitting in core and other libs for some
reason.
the problem is that HB_OUTDEBUG() function is already defined in xhb and
I didn't want to replicate in hbdbgfx (because in xhb it is already
defined either for unix than windows) but for this now hbdbgfx depends
from xhb.
So for me the correct choise is (as you suggest) to move sources from
hbdbgfx to hbmisc (and rename better to hbtools) and also all needed and
common useful functions from xhb to hbmisc, like hboutdbg.c and
hblog.prg leaving in xhb *only* that functions needed to by harbour to
emulate xharbour.
Best Regards
Francesco
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
