Boost C++ Libraries: Ticket #6450: Patch to allow user to specify current filename macro https://svn.boost.org/trac10/ticket/6450 <p> Release revision 85636 </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/6450 Trac 1.4.3 Antony Polukhin Thu, 26 Jan 2012 17:01:38 GMT attachment set https://svn.boost.org/trac10/ticket/6450 https://svn.boost.org/trac10/ticket/6450 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">throw_exception.patch</span> </li> </ul> Ticket Antony Polukhin Thu, 26 Jan 2012 17:02:15 GMT attachment set https://svn.boost.org/trac10/ticket/6450 https://svn.boost.org/trac10/ticket/6450 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">BOOST_THROW_EXCEPTION.patch</span> </li> </ul> Ticket Antony Polukhin Thu, 26 Jan 2012 17:09:22 GMT description changed https://svn.boost.org/trac10/ticket/6450#comment:1 https://svn.boost.org/trac10/ticket/6450#comment:1 <ul> <li><strong>description</strong> modified (<a href="/trac10/ticket/6450?action=diff&amp;version=1">diff</a>) </li> </ul> Ticket Emil Dotchevski Wed, 20 Jun 2012 00:49:27 GMT <link>https://svn.boost.org/trac10/ticket/6450#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/6450#comment:2</guid> <description> <p> I'm wondering if it isn't a better solution to change BOOST_CURRENT_FUNCTION so that it can be overridden globally. I can't think of a use case where I'd be worried about code bloat in BOOST_THROW_EXCEPTION but not in other invokations of BOOST_CURRENT_FUNCTION. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Antony Polukhin</dc:creator> <pubDate>Fri, 22 Jun 2012 15:45:41 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/6450#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/6450#comment:3</guid> <description> <p> Replying to <a class="ticket" href="https://svn.boost.org/trac10/ticket/6450#comment:2" title="Comment 2">emildotchevski</a>: </p> <blockquote class="citation"> <p> I'm wondering if it isn't a better solution to change BOOST_CURRENT_FUNCTION so that it can be overridden globally. I can't think of a use case where I'd be worried about code bloat in BOOST_THROW_EXCEPTION but not in other invokations of BOOST_CURRENT_FUNCTION. </p> </blockquote> <p> BOOST_CURRENT_FUNCTION is used in boost::shared_ptr, boost::function and other libraries when RTTI is disabled. Changing BOOST_CURRENT_FUNCTION will break those libraries </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Emil Dotchevski</dc:creator> <pubDate>Sat, 23 Jun 2012 00:33:07 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/6450#comment:4 https://svn.boost.org/trac10/ticket/6450#comment:4 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> BOOST_THROW_EXCEPTION_CURRENT_FUNCTION available in trunk revision 79033. </p> Ticket Antony Polukhin Mon, 10 Jun 2013 11:37:58 GMT status changed; resolution deleted https://svn.boost.org/trac10/ticket/6450#comment:5 https://svn.boost.org/trac10/ticket/6450#comment:5 <ul> <li><strong>status</strong> <span class="trac-field-old">closed</span> → <span class="trac-field-new">reopened</span> </li> <li><strong>resolution</strong> <span class="trac-field-deleted">fixed</span> </li> </ul> <p> Patch still did not make its way to release branch. </p> Ticket Emil Dotchevski Tue, 10 Sep 2013 05:55:20 GMT status, description changed; resolution set https://svn.boost.org/trac10/ticket/6450#comment:6 https://svn.boost.org/trac10/ticket/6450#comment:6 <ul> <li><strong>status</strong> <span class="trac-field-old">reopened</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> <li><strong>description</strong> modified (<a href="/trac10/ticket/6450?action=diff&amp;version=6">diff</a>) </li> </ul> Ticket