Opened 11 years ago

Closed 11 years ago

#6177 closed Patches (fixed)

increase BOOST_PARAMETER_MAX_ARITY

Reported by: anonymous Owned by: Daniel Wallin
Milestone: To Be Determined Component: parameter
Version: Boost Development Trunk Severity: Problem
Keywords: Cc: tim@…

Description

i've been using boost.parameter extensively with boost.heap and now came to a point, that i need to raise BOOST_PARAMETER_MAX_ARITY to at least 7 in order to be able to compile it.

i am planning to merge boost.heap into trunk in the next few days, so i wonder, would it be reasonable to increase the default of this value to e.g. 8 (patch attached)? currently, boost.heap defines BOOST_PARAMETER_MAX_ARITY before including boost/parameter.hpp, but this will break, if boost/parameter.hpp is included before the boost.heap headers.

it would be great, if the default would be high enough to compile all boost libraries, or could this cause any issues?

Attachments (1)

boost_parameter.patch (1.7 KB ) - added by anonymous 11 years ago.

Download all attachments as: .zip

Change History (7)

by anonymous, 11 years ago

Attachment: boost_parameter.patch added

comment:1 by tim, 11 years ago

Summary: increase BOOST_PARAMETER_MAX_ARITY From: Tim Blechmann <tim@klingt.org>increase BOOST_PARAMETER_MAX_ARITY

comment:2 by tim@…, 11 years ago

Cc: tim@… added

comment:3 by Dave Abrahams, 11 years ago

Please run some tests to see how increasing the arity affects compilation time, say, for the parameter lib tests. If the effect is negligible please go ahead and apply the patch.

Thanks

comment:4 by tim@…, 11 years ago

compiling compile time for libs/parameter/test/basics.cpp hardly changes between values of 5 and 8. with an arity of 32 or 64, compile time increases drastically.

comment:5 by Dave Abrahams, 11 years ago

Then you have my blessing (but I don't have time to do it myself right now).

comment:6 by timblechmann, 11 years ago

Resolution: fixed
Status: newclosed

patch applied

Note: See TracTickets for help on using tickets.