You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@stdcxx.apache.org by "Martin Sebor (JIRA)" <ji...@apache.org> on 2008/01/23 04:54:34 UTC

[jira] Updated: (STDCXX-43) names of atomic functions inconsitent

     [ https://issues.apache.org/jira/browse/STDCXX-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Sebor updated STDCXX-43:
-------------------------------

              Severity: Cosmetic
         Fix Version/s:     (was: 4.2.1)
                        5.0
    Remaining Estimate: 4h
     Original Estimate: 4h

Most of this is already done but changing the rest would be a binary incompatible change. Deferred until 5.0.

> names of atomic functions inconsitent
> -------------------------------------
>
>                 Key: STDCXX-43
>                 URL: https://issues.apache.org/jira/browse/STDCXX-43
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 4.1.2
>         Environment: all
>            Reporter: Martin Sebor
>            Assignee: Martin Sebor
>            Priority: Trivial
>             Fix For: 5.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The names of the implementation-specific atomic functions are inconsistent: some contain the width of the type they operate on (such as __rw_atomic_add32()), others don't (e.g., __rw_atomic_add32()), and others still follow a different naming convention altogether (e.g., __rw_atomic_incr32()). This makes understanding and writing the generic overloads that use them (e.g., __rw_atomic_preincrement(), etc.) difficult and leads to lots of duplicate code in rw/_mutex.h. This is a placeholder issue to rename these functions using a consistent naming convention and to simplify rw/_mutex.h.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.