C++ Extensions for Library Fundamentals, Version 2 (N4564) introduces the type std::experimental::source_location
.
§ 14.1.2 [reflection.src_loc.creation] says:
static constexpr source_location current() noexcept;
Returns: When invoked by a function call (C++14 § 5.2.2) whose postfix-expression is a (possibly parenthesized) id-expression naming
current
, returns asource_location
with an implementation-defined value. The value should be affected by#line
(C++14 § 16.4) in the same manner as for__LINE__
and__FILE__
. If invoked in some other way, the value returned is unspecified.Remarks: When a brace-or-equal-initializer is used to initialize a non-static data member, any calls to
current
should correspond to the location of the constructor or aggregate initialization that initializes the member.[ Note: When used as a default argument (C++14 § 8.3.6), the value of the
source_location
will be the location of the call tocurrent
at the call site. — end note ]
If I understand correctly, then the feature is intended to be used like this.
#include <experimental/source_location> // I don't actually have this header
#include <iostream>
#include <string>
#include <utility>
struct my_exception
{
std::string message {};
std::experimental::source_location location {};
my_exception(std::string msg,
std::experimental::source_location loc = std::experimental::source_location::current()) :
message {std::move(msg)},
location {std::move(loc)}
{
}
};
int
do_stuff(const int a, const int b)
{
if (a > b)
throw my_exception {"a > b"}; // line 25 of file main.cxx
return b - a;
}
int
main()
{
try
{
std::cout << do_stuff(2, 1) << "\n";
}
catch (const my_exception& e)
{
std::cerr << e.location.file_name() << ":" << e.location.line() << ": "
<< "error: " << e.message << "\n";
}
}
Expected output:
main.cxx:25: error: a > b
Without std::experimental::source_location
, we might have used a helper macro THROW_WITH_SOURCE_LOCATION
that internally makes use of the __FILE__
and __LINE__
macros to initialize the exception object properly.
I was wondering how a library could implement std::experimental::source_location
. Unless I'm completely missing the point, doing so is not possible without special compiler support. But what kind of magic compiler features would be needed to make this work? Would it be comparable to the trick deployed for std::initializer_list
? Is there any experimental implementation of this feature available to look at? I have checked the SVN sources for GCC but didn't find anything yet.
Implementing this will require support from the compiler. For instance, with gcc, you could possibly use built-ins functions like
int __builtin_LINE()
This function is the equivalent to the preprocessor
__LINE__
macro and returns the line number of the invocation of the built-in. In a C++ default argument for a functionF
, it gets the line number of the call toF
.const char * __builtin_FUNCTION()
This function is the equivalent to the preprocessor
__FUNCTION__
macro and returns the function name the invocation of the built-in is in.const char * __builtin_FILE()
This function is the equivalent to the preprocessor
__FILE__
macro and returns the file name the invocation of the built-in is in. In a C++ default argument for a functionF
, it gets the file name of the call toF
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With