3 ms·
> Whereas gcc’s cleanup attribute is attached to functions, POSIX’ cleanup functions and the try/finally are attached to possibly nested blocks. > This indicat
by eqvinox 5y ago
> Whereas gcc’s cleanup attribute is attached to functions, POSIX’ cleanup functions and the try/finally are attached to possibly nested blocks.
> This indicates that existing mechanism in compilers may have difficulties with a block model.
Erm. No. GCC's cleanup attribute is attached to nested blocks. Whatever that means for the conclusion there.
How is a pretty basic misunderstanding like this seeping into an ISO WG document?!?
[add.:] in case anyone wants to double check: https://gist.github.com/eqvinox/c062f5a46f3a60b1151fcdf3e91a6da0 https://gist.github.com/eqvinox/c062f5a46f3a60b1151fcdf3e91a...
- tialaramex 5y agoAn individual or handful of people make a proposal, the Working Group looks at the proposal, maybe it gets revised (this is version 2). Working Groups themselves do not, on the whole, produce documents like this. There is no ISO magic ensuring working groups are all-knowing. There's an excellent chance that no members of WG14 have a deep in-depth knowledge of GCC, or that members who did they weren't particularly interested in that part of this paper (e.g. they were already staunchly for or against, remember ISO Working Groups are democratic, a proposal does not need consensus, so a working group member who thinks your idea is inherently good or bad might just skim the introduction, and move on)