I have heard since long that HB_NOSTARTUPWINDOW is a
__dirty__|__horrible__|__etc__ hack.
May be due to my little understanding of other compilers etc. o
due to lack of sufficient programming knowledge, I have never
been able to understand the rationale behind it. I could never
grasp why a call to find a dynsym makes the code hacky.
I am persuing to reintroduce it any way.
Can you please enlighten me why you consider it so?
Pritpal,
Your solution is a bad shortcut, which targets to
solve your sole personal need inside core Harbour,
executed in the "rope and glue" kind of way, sorry
to say that. The solution is largely inelegant, and
it just adds yet another complication while not
giving too much to the general "feature set".
Harbour tries to be a well thought out and a well
executed language, and this hack simply doesn't fit
the picture.
I've told my reasons several times BTW, but you
still couldn't tell even one reason while current
system is any bad, or why isn't it good enough to
add this hack to GTWVG, where such hacks are
accepted if you really need it. [ If it's there
already, I simply cannot imagine why do you want
to force it to core also. ]
So pls everyone try to think of the bigger picture
when trying to solve some personal needs. It's
certainly not a solution to add a distinct switch
for every such occasion, as we'd probably already
have several hundreds of command line options, function
variations and probably also a thousand build-time,
compile-time, link-time, runtime and dynsym switches.
Imagine anyone trying to use, debug or support such
a system.
In case of HB_NOSTARTUPWINDOW, we have a clearly
superior solution now, so we should try to solve
any possible problems with it, rather than trying
to go back in time and destroy what we have.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
