Can we consider BOOST_DEDUCED_TYPENAME deprecated?
Hi! I'm finally getting around to spending some decent time tackling tickets on Boost.Range and I'm finding the rather verbose BOOST_DEDUCED_TYPENAME to be considerably worsening the readability of my new code. I believe this existed to cope with very old compilers which we no longer officially support in new versions of Boost. Should I continue to put this in, or is it reasonably to drop a painful workaround for such an old compiler issue? Neil Groves
On 26 February 2014 15:27, Neil Groves
I'm finally getting around to spending some decent time tackling tickets on Boost.Range and I'm finding the rather verbose BOOST_DEDUCED_TYPENAME to be considerably worsening the readability of my new code. I believe this existed to cope with very old compilers which we no longer officially support in new versions of Boost.
Should I continue to put this in, or is it reasonably to drop a painful workaround for such an old compiler issue?
It's up to you, but I stopped using it years ago. AFAIK it's only the free Borland command line compiler which needs it. I might leave it in old code, but I wouldn't use it in anything new.
participants (2)
-
Daniel James -
Neil Groves