Opened 11 years ago
Closed 9 years ago
#6450 closed Patches (fixed)
Patch to allow user to specify current filename macro — at Version 6
| Reported by: | Antony Polukhin | Owned by: | Emil Dotchevski |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | exception |
| Version: | Boost 1.48.0 | Severity: | Optimization |
| Keywords: | Cc: | antoshkka@… |
Description (last modified by )
Release revision 85636
Change History (8)
by , 11 years ago
| Attachment: | throw_exception.patch added |
|---|
by , 11 years ago
| Attachment: | BOOST_THROW_EXCEPTION.patch added |
|---|
comment:1 by , 11 years ago
| Description: | modified (diff) |
|---|
follow-up: 3 comment:2 by , 10 years ago
comment:3 by , 10 years ago
Replying to emildotchevski:
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.
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
comment:4 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
BOOST_THROW_EXCEPTION_CURRENT_FUNCTION available in trunk revision 79033.
comment:5 by , 9 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Patch still did not make its way to release branch.
comment:6 by , 9 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | reopened → closed |
Note:
See TracTickets
for help on using tickets.
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.