Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#6338 closed Bugs (fixed)

push_front.hpp completely broken

Reported by: smr@… Owned by: Joel de Guzman
Milestone: To Be Determined Component: fusion
Version: Boost 1.48.0 Severity: Problem
Keywords: Cc:

Description

The following simple file does not compile with gcc 4.6.2 on linux:

#include <boost/fusion/algorithm/transformation/push_front.hpp>

Compile errors:

In file included from /usr/include/boost/fusion/view/iterator_range/detail/segments_impl.hpp:13:0,
                 from /usr/include/boost/fusion/view/iterator_range/iterator_range.hpp:21,
                 from /usr/include/boost/fusion/view/iterator_range.hpp:10,
                 from /usr/include/boost/fusion/sequence/intrinsic/detail/segmented_begin.hpp:12,
                 from /usr/include/boost/fusion/sequence/intrinsic/begin.hpp:17,
                 from /usr/include/boost/fusion/view/joint_view/joint_view.hpp:13,
                 from /usr/include/boost/fusion/algorithm/transformation/push_front.hpp:11,
                 from transformation_push_front.cc:1:
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:128:37: error: ‘push_front’ in namespace ‘boost::fusion::result_of’ does not name a type
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:128:47: error: expected template-argument before ‘<’ token
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:128:47: error: expected ‘>’ before ‘<’ token
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:132:13: error: template argument 1 is invalid
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:133:9: error: expected ‘::’ before ‘type’
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp: In static member function ‘static boost::fusion::detail::make_segment_sequence_front<Stack, Size>::type boost::fusion::detail::make_segment_sequence_front<Stack, Size>::call(const Stack&)’:
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:142:17: error: ‘push_front’ is not a member of ‘boost::fusion’
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp: At global scope:
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:405:41: error: ‘push_front’ in namespace ‘boost::fusion::result_of’ does not name a type
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:405:51: error: expected template-argument before ‘<’ token
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:405:51: error: expected ‘>’ before ‘<’ token
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:410:17: error: wrong number of template arguments (1, should be 2)
/usr/include/boost/fusion/algorithm/transformation/push_back.hpp:19:16: error: provided for ‘template<class Sequence, class T> struct boost::fusion::result_of::push_back’
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:411:13: error: template argument 1 is invalid
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:412:9: error: expected ‘::’ before ‘type’
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp: In static member function ‘static boost::fusion::detail::make_segmented_range_reduce2<StackBegin, StackEnd, SameSegment>::type boost::fusion::detail::make_segmented_range_reduce2<StackBegin, StackEnd, SameSegment>::call(StackBegin, StackEnd)’:
/usr/include/boost/fusion/view/iterator_range/detail/segmented_iterator_range.hpp:426:21: error: ‘push_front’ is not a member of ‘boost::fusion’

Attachments (1)

diff (781 bytes ) - added by smr@… 11 years ago.
Cheap fix

Download all attachments as: .zip

Change History (7)

by smr@…, 11 years ago

Attachment: diff added

Cheap fix

comment:1 by Joel de Guzman, 11 years ago

Resolution: fixed
Status: newclosed

comment:2 by smr@…, 11 years ago

What fix was applied?

comment:4 by smr@…, 11 years ago

Can this be pushed to release, please?

in reply to:  4 comment:5 by Joel de Guzman, 11 years ago

Replying to smr@…:

Can this be pushed to release, please?

Just did that 2 days. Pls. check it out (don't have access to my dev system right now). Is there still a problem?

comment:6 by Steve Robbins <smr@…>, 11 years ago

Confirmed it is in release (tested Release Candidate of Feb 20).

Note: See TracTickets for help on using tickets.