On Jan 15, 2010, at 1:53 PM, Krzysztof Kosiński wrote:
This looks good. I think that if the instructions on how to fix the broken hashtable header are included in the Mac compilation instructions, and a check is put in configure, we can use the non-deprecated tr1::unordered_set. What others think?
I think I'd like that in general. I had not had time to chase down all the issues myself, so I stopped at merely encapsulating the Font* abuses (Note that I say "abuse" here, since Inkscape was made to handle fonts in a manner that not is a good way to deal with fonts).
I think all we need to do is
1) get tr1::unordered_set in our matrix of supported features and make sure we know where things cut off.
2) add several CxxTest unit tests to cover things on both unordered_set and hash_set. As long as those are comprehensive, we should be safe.
Thanks, guys, for all the work on this.