RE: DData in hierarchical libraries

Am Donnerstag, 26. Februar 2004 15:07 schrieb JP Bernardy:
[...]
Well, DData is meant to replace Data.Set and Data.FiniteMap, and add some functionality.
Is it for sure that Data.Set and Data.FiniteMap will be replaced by the DData stuff? Will the DData modules get the Data prefix when they are included in the hierarchical libraries?
I would like to see that happen, but I'd like to see more people comment on the design (and performance) of the DData libraries first. The breakage to code will be fairly minimal: Data.FiniteMap can be left in place but deprecated, many of the operations from Data.Set can also be provided by the new Data.Set (but deprecated, of course). The other modules don't conflict. Cheers, Simon

Am Montag, 15. März 2004 12:56 schrieb Simon Marlow:
[...]
Is it for sure that Data.Set and Data.FiniteMap will be replaced by the DData stuff? Will the DData modules get the Data prefix when they are included in the hierarchical libraries?
I would like to see that happen, but I'd like to see more people comment on the design (and performance) of the DData libraries first.
I'm really not a DData expert but it's seems to me that Daan has invested a lot in good design and efficiency. So I would like to see the DData modules as the standard modules under Data, too.
The breakage to code will be fairly minimal: Data.FiniteMap can be left in place but deprecated, many of the operations from Data.Set can also be provided by the new Data.Set (but deprecated, of course). The other modules don't conflict.
By the way, is there already a mechanism for marking deprecated code? Will deprecated code be removed some time or will it pollute the libraries until the end of time?
Cheers, Simon
Wolfgang

Simon Marlow wrote:
Is it for sure that Data.Set and Data.FiniteMap will be replaced by the DData stuff? Will the DData modules get the Data prefix when they are included in the hierarchical libraries?
I would like to see that happen, but I'd like to see more people comment on the design (and performance) of the DData libraries first.
I've taken Daan's DData half a year ago and replaced all our uses of Data.FiniteMap (I never liked Data.Set based on FiniteMap), because I was convinced that DData was (and still is!) superior. I made no performance test, but never observed unexpected bad performance (or even bugs). Christian
participants (3)
-
Christian Maeder
-
Simon Marlow
-
Wolfgang Jeltsch