Hi Przemek,
may be called by them. Surely, a command-line switch would
be easier for normal usage. Anyhow we can revisit this later.
Our main() function is executed _AFTER_ first calls to hb_xgrab().
Each PCODE module and some subsystems' (like GT or RDD) initial code
is executed _BEFORE_
On Thu, 16 Oct 2008, Szak�ts Viktor wrote:
Hi Viktor,
When HB_FM_STATISTICS_DYN (or default) is used,
one could simply turn on stats using command line
switch --fmstat, or setting up HARBOUR envvar
with --fmstat for example on development envs.
I'll add support for HB_FM_STATISTICS_DYN but
Hi Przemek,
Many thanks for your efforts. Not making it the default
is okay with me personally, but for the project itself
most complications would still remain this way. I'd suggest
to measure the speed loss to compare with possible benefits.
Besides making this a runtime option, IMO it would
On Fri, 17 Oct 2008, Szak�ts Viktor wrote:
Hi Viktor,
Many thanks for your efforts. Not making it the default
is okay with me personally, but for the project itself
most complications would still remain this way. I'd suggest
to measure the speed loss to compare with possible benefits.
The
Hi Przemek,
What do you think of making the choice
between stats on or off via a command line
switch or envvar? Currently both the non-GNU
and the non-GNU ways or choosing between these
are cumbersome, and there is no way to turn
stats on on the field if leakage or corruption
is suspected.
To
On Thu, 16 Oct 2008, Szak�ts Viktor wrote:
Hi Viktor,
What do you think of making the choice
between stats on or off via a command line
switch or envvar? Currently both the non-GNU
and the non-GNU ways or choosing between these
are cumbersome, and there is no way to turn
stats on on the
Hi Przemek,
What do you think of making the choice
between stats on or off via a command line
switch or envvar? Currently both the non-GNU
and the non-GNU ways or choosing between these
are cumbersome, and there is no way to turn
stats on on the field if leakage or corruption
is suspected.
Hi Przemek,
Just to give a simple practical example. To avoid
leaks and potential memory corruption problems in
my app, I'd like to have FM stats 'on' for selected
customers, selected versions, selected usages or
time periods. But, I'd also like to avoid all the
problems with building,
