From owner-freebsd-doc@FreeBSD.ORG  Sat Oct 18 11:08:39 2014
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Delivered-To: freebsd-doc@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 6276A56B
 for <freebsd-doc@FreeBSD.org>; Sat, 18 Oct 2014 11:08:39 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 496E2116
 for <freebsd-doc@FreeBSD.org>; Sat, 18 Oct 2014 11:08:39 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9IB8dLR051315
 for <freebsd-doc@FreeBSD.org>; Sat, 18 Oct 2014 11:08:39 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-doc@FreeBSD.org
Subject: [Bug 194280] pthread_cleanup_push, pthread_cleanup_pop manual pages
 are missing critical usage information.
Date: Sat, 18 Oct 2014 11:08:39 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Documentation
X-Bugzilla-Component: Documentation
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: easy
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: jhb@FreeBSD.org
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-doc@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status cc
Message-ID: <bug-194280-9-xE76KZJ0qm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-194280-9@https.bugs.freebsd.org/bugzilla/>
References: <bug-194280-9@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Oct 2014 11:08:39 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194280

John Baldwin <jhb@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Needs Triage                |In Discussion
                 CC|                            |jhb@FreeBSD.org

--- Comment #2 from John Baldwin <jhb@FreeBSD.org> ---
I went with language similar to that of POSIX:

     The pthread_cleanup_push() function is implemented as a macro that opens
     a new block.  Invocations of this function must appear as standalone
     statements that are paired with a later call of pthread_cleanup_pop(3) in
     the same lexical scope.

for push and

     The pthread_cleanup_push() function is implemented as a macro that closes
     a block.  Invocations of this function must appear as standalone state-
     ments that are paired with an earlier call of pthread_cleanup_push(3) in
     the same lexical scope.

"same lexical scope" already implies same code block in same function.  I don't
know that we need to explicitly call out the that using the API incorrectly
will result in compile errors.  The same is true of any number of other APIs
(e.g. trying to pass a pointer to the getchar() or putchar() "functions" (which
are also macros).

-- 
You are receiving this mail because:
You are the assignee for the bug.