Viktor Szakáts wrote:
>
> Another comment:
>
> You started to add *_DBG() functions. Here it's called HBIDE_DBG().
> But why not use HB_TRACELOG( params ) instead, if you want to force
> trace calls in live code? F.e. HB_TRACELOG( "hello" )
>
> Anyhow it's much more efficient to use 'HB_TRACE()' since it will be
> excluded from code for final builds, and not causing any slowdowns
> because of permanently switched on logging.
>
> Some of these may apply to HBXBP and HBQT, I didn't check what is
> exactly used there.
>
You are right.
This small code snipper I pulled from testing hbide.prg so
these surfaced as is. Just a little lazyness.
These calls just separate logging code from .cpp files, nothing else.
BTW, without looking at the logs, only glaring the
Windows task manager will reveal how mem is consumed with every
call to messageBox().
-----
enjoy hbIDEing...
Pritpal Bedi
_a_student_of_software_analysis_&_design_
--
View this message in context:
http://n2.nabble.com/hbQT-c-stub-GC-Some-food-for-thoughts-tp4483724p4491397.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
