Hi Francesco,
and at C level is similar also if I have not already added
hb_OutDebug equivalent for linux.
So now it works both in window and linux only from PRG level (using
hboutdbg.c functions from xhb), instead at C level *actually* it
works only for windows.
The real problem here is that (besides the different
API implementation depending on platform), is that
also that some platform needs xhb, some not.
So, optimally there should be no difference between
either APIs and lib dependencies when jumping
platforms. Also xhb lib dependency is not very
welcome for any Harbour contribs, especially if the
goal is to present an enhanced version of an existing
xhb API.
I'd propose to move these functions inside
xhb lib, in case someone wants to deal with
the details of this, if not, and there are no
better ideas, I'll remove this lib from the
repository.
If you think that I can make above modifications (add C level call
for them that alter code, also if just a little, from original
xharbour file) I agree to move hbdbgfx into xhb.
I think this would be the best. The purpose of xhb lib
in Harbour is to present extra xhb functionality for
Harbour users (and former xhb users). We don't have any
strict rules to stay 100.00% compatible with xhb. There
is also no rule that we couldn't _enhance_ or fix xhb
functions while staying fully/mainly compatible on
the API level. I think your work fits these descriptions.
Otherwise I will add above changes to hbdbgfx to make it complete.
Take your decision, I will follow it. If you want to delete hbdbgfx
lib at all I will continue to have it in my repository as before.
I have added it because I thought it can be useful to someone.
My vote is to implement your solution inside xhb lib,
this way the already known xhb API will get a better
implementation, and everyone can just as well use it
by linking xhb lib.
[ Maybe it or its parts can once be made the default
Harbour logging facility (probably under different
API names). In my understanding though, logging should
be fully portable and solved using just the basic file
functions and possibly some prospects to make sure no
log entries are lost, even in case the target disk is
temporarily inaccessible). ]
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
