Hi Lorenzo,
Il 27/10/2008 6.11, Lorenzo Fiorini ha scritto:
On Sun, Oct 26, 2008 at 11:24 PM, Francesco Saverio Giudice
[EMAIL PROTECTED] wrote:
if you added this function thinking that I miss it, note that correct
hb_OutDebug() is in xhb lib and you need to add it to link phase.
I think that
On Mon, Oct 27, 2008 at 1:25 PM, Francesco Saverio Giudice [EMAIL PROTECTED]
I know them well and also for me them have to be moved outside from xhb.
Probably into hbmisc (as proposed from Viktor to be renamed to hbtools).
IMHO logging and xml are useful, general and distinct tasks.
I suggest
These are xhb compatibility functions with xhb specific
implementations and names, headers. They can be used
without any kind of side effects by linking xhb lib.
I see no point in picking selected xhb functions
and shuffling them around to other libs. This creates
far more problems than it may
I know them well and also for me them have to be moved outside from
xhb.
Probably into hbmisc (as proposed from Viktor to be renamed to
hbtools).
IMHO logging and xml are useful, general and distinct tasks.
I suggest to create a contrib/hblog and contrib/hbxml so that every
developer can
On Mon, Oct 27, 2008 at 1:44 PM, Szakáts Viktor [EMAIL PROTECTED] wrote:
If there is anything that can be done to untie current
implementation living inside xhb from other xhb parts,
we should do it right there.
IMHO xhb has wrongly mixed libs and language compatibility services.
hblog and
On 2008.10.27., at 14:42, Lorenzo Fiorini wrote:
On Mon, Oct 27, 2008 at 1:44 PM, Szakáts Viktor harbour.
[EMAIL PROTECTED] wrote:
If there is anything that can be done to untie current
implementation living inside xhb from other xhb parts,
we should do it right there.
IMHO xhb has
On Mon, Oct 27, 2008 at 3:00 PM, Szakáts Viktor [EMAIL PROTECTED] wrote:
Lastly, and this hasn't been answered yet by
you, yet it seems the most important question:
What is the problem with using xhb.lib if you
need this functionality? It's there, maintained
and working.
Because xhb makes
On Mon, 27 Oct 2008, Lorenzo Fiorini wrote:
Hi Lorenzo,
that I don't need and that can potentially change normal Harbour behaviour.
F.e. is HB_DESERIALIZE in rtl the same as the one in xhb?
XHB lib does not have HB_DESERIALIZE. It has only HB_DESERIALBEGIN()
HB_DESERIALNEXT() redirected to
On Mon, Oct 27, 2008 at 5:37 PM, Przemyslaw Czerpak [EMAIL PROTECTED] wrote:
XHB lib does not have HB_DESERIALIZE. It has only HB_DESERIALBEGIN()
HB_DESERIALNEXT() redirected to Harbour core serialization code but
there are in practice dummy functions.
This is the problem xhb has real
I agree that some things in XHB library can change standard HVM
behavior
and it's wrong that they are not separated because it effects also
other
code.
IMHO xhb should be used only by developers that want to port xHarbour
code as it is.
Standard Harbour users should not have to use it.
Hi Pritpal,
Il 26/10/2008 3.14, Pritpal Bedi ha scritto:
2008-10-25 19:10 UTC-0800 Pritpal Bedi ([EMAIL PROTECTED])
* harbour/contrib/hbdbgfx/dbgfx.c
+ HB_FUNC( HB_OUTDEBUG ).
May be I am missing something. Please correct.
Regards
Pritpal Bedi
if you added this function
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
On Sun, Oct 26, 2008 at 11:24 PM, Francesco Saverio Giudice
[EMAIL PROTECTED] wrote:
if you added this function thinking that I miss it, note that correct
hb_OutDebug() is in xhb lib and you need to add it to link phase.
I think that we can move hblog.prg and hboutdbg.c in hbdbgfx lib.
As I
2008-10-25 19:10 UTC-0800 Pritpal Bedi ([EMAIL PROTECTED])
* harbour/contrib/hbdbgfx/dbgfx.c
+ HB_FUNC( HB_OUTDEBUG ).
May be I am missing something. Please correct.
Regards
Pritpal Bedi
--
View this message in context:
14 matches
Mail list logo
