On Mon, 29 Mar 2010, Szak�ts Viktor wrote: Hi,
> Looks like we're starting to resemble xhb. I hope not. xHarbour reach the level where core developers have serious problems to control the code and understand/know all hacks inside and all internal dependencies created by direct accessing of HVM structures. I hope that sth like that will not happen with Harbour. It's very important to use only documented API (BTW this code example can be written using only document API functions) In the worst case we will have to create list of users using such hacks to ignore any bug reports from them. I do not plan to wast my time looking for GPF or any other problems if they can be caused by none core code accessing HVM internals. I still remember how I was working on xHarbour core code and I'm very happy that now I do not have to spend most of my devel time looking for the any interactions with any other code accessing HVM internals when I wanted to change sth or looking for reasons of some GPFs or or other unexpected problems reported by users. Current Harbour core code is still not perfect but for sure much much better then xHarbour one so working on core code is much more efficient. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
