Re: [Boost-bugs] [Boost C++ Libraries] #8463: function_output_iterator: MSVC warning C4512

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8463: function_output_iterator: MSVC warning C4512
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-07-02 18:08:07

#8463: function_output_iterator: MSVC warning C4512
  Reporter: Mike Cowperthwaite | Owner:
  <michael.cowperthwaite@…> | jeffrey.hellrung
      Type: Bugs | Status: new
 Milestone: To Be Determined | Component: iterator
   Version: Boost 1.52.0 | Severity: Problem
Resolution: | Keywords:

Comment (by Mike Cowperthwaite <michael.cowperthwaite@…>):

 1) fmhess's 'advice' at that other bug looks like knee-jerk Microsoft-
 blaming, altho he might technically be right that these warnings are
 spurious. (a) As noted in the original report here, several Boost
 libraries have already taken steps to prevent them. (b) A spurious warning
 here might be a non-spurious warning elsewhere; and this warning cannot be
 suppressed using MS's `#pragma warning`.

 2) Not sure which "problem solution above" you're referring to: there is
 code in comment 2, and code in the original report. The code in the
 original report is similar to the solutions I found in other Boost
 libraries. The code in comment 2 looks like it might work fine; whether
 copying a `UnaryFunction` object with every instance of `output_proxy`
 would be undesirable overhead, I cannot say.

 I'm curious to know if Paul Saville's `assert()` has ever been triggered.
 (Also, Paul correctly pinned the cause on the "reference member variable,"
 not a "const data member" as I originally stated.)

Ticket URL: <>
Boost C++ Libraries <>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:13 UTC