From owner-freebsd-arch@FreeBSD.ORG Thu Apr 24 01:32:03 2008 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD5391065683 for ; Thu, 24 Apr 2008 01:32:03 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 93A7D8FC1D for ; Thu, 24 Apr 2008 01:32:03 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (HPooka@thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.2/8.14.2) with ESMTP id m3O1HQuw065687 for ; Wed, 23 Apr 2008 20:17:26 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Wed, 23 Apr 2008 20:17:26 -0500 (CDT) From: "Sean C. Farley" To: freebsd-arch@FreeBSD.org Message-ID: User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-2.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, URIBL_AB_SURBL, URIBL_JP_SURBL, URIBL_SC_SURBL autolearn=no version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mail.farley.org Cc: Subject: API type/include corrections X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Apr 2008 01:32:03 -0000 I am going through a list where I track items I wish to fix as I run across them. I just like to make sure they are actually broken before fixing them. :) The items in question: 1. Should the man page for mkdir(2) include sys/types.h? Open Group docs[1] do not have it, yet they do use it in the example. It is not needed to compile their example. 2. Should readpassphrase(3) include sys/types.h in the man page, or should it be added to readpassphrase.h? It is needed to compile even a simple program to pick up size_t. 3. Should chflags(2), lchflags(2) and fchflags(2) have the flags argument be of type fflags_t (uint32_t) instead of u_long? The man page says u_long while the type for st_flags in struct stat is fflags_t. Sean 1. http://www.opengroup.org/onlinepubs/000095399/functions/mkdir.html -- scf@FreeBSD.org