Page 1 of 1
What they are thinking?
Posted: Tue Jan 19, 2010 6:12 am
by sudip
Hello Friends,
Can we have a special section to see what developments are going on with different libraries of Harbour and even xHarbour?
There is nothing similar like this in the whole world of Harbour and xHarbour.
Please forgive me if I am telling something wrong
With best regards.
Sudip
Re: What they are thinking?
Posted: Fri Mar 26, 2010 11:44 am
by swapan
sudip wrote:Hello Friends,
Can we have a special section to see what developments are going on with different libraries of Harbour and even xHarbour?
There is nothing similar like this in the whole world of Harbour and xHarbour.
Please forgive me if I am telling something wrong
With best regards.
Sudip
My 2 cents ........
We should be aware of the new developments,ideas floating in the Harbour/xHarbour communities.
As all had the common "ancestor" - CLIPPER. May be we are more like a family but we should pay attention to the new developments happening in Harbour/Xharbour platforms.
Re: What they are thinking?
Posted: Fri Mar 26, 2010 1:05 pm
by gfilatov
Hello Sudip,
It is a very well suggestion
There is a
changelog file in the Harbour SVN for that information.
F.e., for now the Harbour guru Przemyslaw Czerpak was uploaded an updated memory allocator to DLMALLOC 2.8.4 from 2.83 version for the current Harbour SVN (great contribution
). You can read more about this at
http://gee.cs.oswego.edu/dl/html/malloc.html
History:
V2.8.4 Wed May 27 09:56:23 2009 Doug Lea (dl at gee)
* Use zeros instead of prev foot for is_mmapped
* Add mspace_track_large_chunks; thanks to Jean Brouwers
* Fix set_inuse in internal_realloc; thanks to Jean Brouwers
* Fix insufficient sys_alloc padding when using 16byte alignment
* Fix bad error check in mspace_footprint
* Adaptations for ptmalloc; thanks to Wolfram Gloger.
* Reentrant spin locks; thanks to Earl Chew and others
* Win32 improvements; thanks to Niall Douglas and Earl Chew
* Add NO_SEGMENT_TRAVERSAL and MAX_RELEASE_CHECK_RATE options
* Extension hook in malloc_state
* Various small adjustments to reduce warnings on some compilers
* Various configuration extensions/changes for more platforms. Thanks
to all who contributed these.
V2.8.3 Thu Sep 22 11:16:32 2005 Doug Lea (dl at gee)
* Add max_footprint functions
* Ensure all appropriate literals are size_t
* Fix conditional compilation problem for some #define settings
* Avoid concatenating segments with the one provided
in create_mspace_with_base
* Rename some variables to avoid compiler shadowing warnings
* Use explicit lock initialization.
* Better handling of sbrk interference.
* Simplify and fix segment insertion, trimming and mspace_destroy
* Reinstate REALLOC_ZERO_BYTES_FREES option from 2.7.x
* Thanks especially to Dennis Flanagan for help on these.
I hope that give you an idea
Re: What they are thinking?
Posted: Fri Mar 26, 2010 2:14 pm
by luisvasquezcl
Dear,
I think it is good idea to go Sudip knowing that progress and what's new at harbor.
I would also be interesting to discuss some features that exist but no documentation as we know they exist.
We are grateful to Grigory who is always careful as to share their knowledge.
Best regards,
Luis Vasquez
Re: What they are thinking?
Posted: Fri Mar 26, 2010 3:56 pm
by sudip
Thanks a lot Grigory
With best regards.
Sudip