This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Exceptions declaration and static analysis
- From: dvd <dvd+nntp at gnx dot it>
- To: gcc-help at gcc dot gnu dot org
- Date: Fri, 29 Jan 2016 15:54:07 +0100
- Subject: Re: Exceptions declaration and static analysis
- Authentication-results: sourceware.org; auth=none
- References: <slrnnamsfi dot j3u dot dvd+nntp at sdentato dot gnx dot it> <CAH6eHdQ7-Gcnb9=JfxhWRv=yEDCKwXvo-j_+USBswpnCEG6j8g at mail dot gmail dot com>
On 2016-01-29, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 29 January 2016 at 14:06, dvd wrote:
>> Is this a totally waste of time and energy? Or it could be useful (even if not
>> 100% accurate)?
>
> I was surprised not to see any mention of C++98 exception
> specifications in your mail.
I didn't mention it because it is now deprecated and my brain
automatically switched to an attributes based approach.
> They aren't statically checked, but I don't see a need to invent a new
> attribute to re-declare the information they can already provide. Do
> you simply want to avoid the deprecated feature?
Yes, but I'm open to any suggestions.
>
> Are you only checking throw expressions in the function itself, or
> transitively checking the attribute on all called functions?
The grand plan is to check the attribute on every called function