tuples even at a cost of extended compilation time. Using boost/preprocessor library, it is relatively easy to rewrite the tuple code in such a way
"Max Motovilov" <max@yymap.com> wrote that
arity limit will depend on a single configuration macro without incuring any other changes to the library. No additional cost will be imposed on the users who are satisifed with the current tuple library.
There may be problems with Boost.Preprocessor: 1. different compiler have different max limits on code outputted from expanded macro. E.g. BCB has quite low limit (somewhere 1-2kB of text). When this limit is reached, BCB starts to behave unpredictably. 2. compilers based on EDG frontend take exponential time to process some Boost.PP statements. This is problem e.g. of Intel C++ compiler. One way to avoid the problems above is to use local or file iteration technique, available in Boost.PP. It would be good to test impact of your change on as many compilers as possible. /Pavel