Date: Mon, 28 Apr 2025 09:12:12 +0100
On Mon, Apr 28, 2025 at 7:00 AM Julian Waters wrote:
>
> I can't address every point, but the point I was making is that I
> *don't* want to have to use noexcept everywhere, but as it stands now
> you *have* to do that if you so much as have 1 function you want to be
> noexcept (Such as operator new for instance) but don't want the
> handlers in the final binary for certain reasons. As in, if you have 1
> function that needs to be throw() which calls other functions, those
> other functions and the functions they in turn call have to be throw()
> as well, which gets tedious to do really quickly.
Unless there were to be a new namespace for the 'noexcept' functions. Like this:
namespace std {
char* strcpy( char* dest, const char* src );
namespace noexcepts {
char* strcpy( char* dest, const char* src ) noexcept;
}
}
>
> I can't address every point, but the point I was making is that I
> *don't* want to have to use noexcept everywhere, but as it stands now
> you *have* to do that if you so much as have 1 function you want to be
> noexcept (Such as operator new for instance) but don't want the
> handlers in the final binary for certain reasons. As in, if you have 1
> function that needs to be throw() which calls other functions, those
> other functions and the functions they in turn call have to be throw()
> as well, which gets tedious to do really quickly.
Unless there were to be a new namespace for the 'noexcept' functions. Like this:
namespace std {
char* strcpy( char* dest, const char* src );
namespace noexcepts {
char* strcpy( char* dest, const char* src ) noexcept;
}
}
Received on 2025-04-28 08:12:20