Hi Pritpal,
<<<
I'd suggest to step over stirct personal needs when
it comes to developing Harbour.
I do not use GTWVT either. All my developments are on GTWVG.
May be it counter your suspicion.
<<<
I'm trying to leave unnecessary options and hacks out of
Harbour, because all these just raise questions and
create problems with no gain. There is not much point
in maintaining one good and one bad solution in parallel,
as the resources are scarce.
You have better goal concepts with you.
So if you feel it right remove HB_NOSTARTUPWINDOW.
Hope you will not force this on GTWVG anyway.
GTWVG is a contrib, and contribs (especially if actively
maintained) are private areas. The only thing
I "personally" care about them in general is that they
compile cleanly on all supported platforms. If they
don't, they should either be fixed or properly guarded.
Everything above that is an "extra".
We're at the stage where almost everything compiles
cleanly (at least on Windows and major compilers). Next
stage can be to actually fix / enhance functionality
where needed, and raise code quality / consistency.
As for building cleanly:
GCC 4.12/4.30 are the most picky compilers, and the
only contribs not building cleanly are these:
4.12:
- hbw32 / OLE (known hacks in code)
- hbole (hacks in code)
- hbfbird (longlong problems)
- hbsqlit2 / hbsqlit3 (foreign code only)
- hbwhat32
- hbziparch (this code is close to a disaster)
- rddads (foreign header)
(all .logs are available on sf.net BTW)
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
