In fact the whole point of previous implementation was that we warn developers if there _is_ a leak, and stay silent if there isn't. This way it's apparent when there is a problem and when not. If we wash together the two messages, it will be less easy to spot if there is a problem. I can imagine a 'zero' value could be useful for testers to see there _was_ testing/measurement done, yet the result is zero. Probably that's the reason Istvan added it.
An interesting task would be to find out a method to ensure that only Harbour memory allocation functions were used throughout the whole app (even C++ allocators), otherwise we may get into false impressions. Brgds, Viktor On 2010 Jan 3, at 00:36, Mindaugas Kavaliauskas wrote: > Hi, > > > Bisz István wrote: >> Total memory allocated: 2251241 bytes (29215 block(s)) >> Warning, memory allocated but not released: 0 bytes (0 block(s)) > > So, let's print a single line joined message: > > Total memory allocated: 2251241 bytes (29215 block(s)), not released: 0 bytes > (0 block(s)) > > if these zeros are important, otherwise message looks redundant. > > > Regards, > Mindaugas > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
