From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) by sourceware.org (Postfix) with ESMTPS id 05E463842431 for ; Fri, 19 Mar 2021 20:35:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 05E463842431 Received: by mail-wm1-x331.google.com with SMTP id g20so6099541wmk.3 for ; Fri, 19 Mar 2021 13:35:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=xguUs7KhjI6HHnwjKnATX81dPZ2l9/KI4cGLompbbVA=; b=a1wHyWU6pe0oz5uhQTP0WpwqadBMpox4n5QhW9LwKL58s7RwinbOXFVqKzlXJ5YMwB pXR4FzQj9LwdiOw24f30L6H4KHXkKTOg5plTl0lCW+j73cgBncgAXLSqwzeeR0ZLqjQr 2HX4lSdY9T1tNi3in8oReAJe35Z46TSulTYKWZY1KrP3pH72wTurTx+nO5K8HUdupexK HDOWXA60xjwQ7CD5hqnjvlga0g4+CdLnODJWZF4Fplfccvc85sYrYz3Kvi7JnEBg6jmg ZKssugE0YttcznCEum5AZGpo8HN4+K1TD81B1eXdEu4Yun7TPcOuUQfdwt+vUAoahd6K EENA== X-Gm-Message-State: AOAM531GtQS/JhO4QiXopykvInXSpNqXf+OcaqGudCdnF7ZgbWPlAvaj JsgDWAHlUgOb6fo8oZDpY4g= X-Google-Smtp-Source: ABdhPJwsAfFk8zVoup3uZDKTQXM7HhJEcvXbeBe2wA4+zt9OMpKPxj3dUSC6VXgPt2aLt824WA26jA== X-Received: by 2002:a05:600c:4fcb:: with SMTP id o11mr5268714wmq.117.1616186103146; Fri, 19 Mar 2021 13:35:03 -0700 (PDT) Received: from [192.168.0.160] ([170.253.36.171]) by smtp.gmail.com with ESMTPSA id n6sm11357588wrw.63.2021.03.19.13.35.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 19 Mar 2021 13:35:02 -0700 (PDT) Subject: Re: [PATCH] Various pages: Remove unused To: Joseph Myers , Zack Weinberg Cc: linux-man , GNU C Library , "Michael Kerrisk (man-pages)" References: <20210314160134.127878-1-alx.manpages@gmail.com> From: "Alejandro Colomar (man-pages)" Message-ID: <574cb3b0-bc99-2c19-2647-566916b9826a@gmail.com> Date: Fri, 19 Mar 2021 21:35:01 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2021 20:35:05 -0000 Hi Joseph, On 3/15/21 7:25 PM, Joseph Myers wrote: > On Sun, 14 Mar 2021, Zack Weinberg wrote: > >> I endorse this change. For glibc, if the header file containing the >> function prototype doesn't also provide everything you need to call >> the function, it's a bug (except for a few cases where the relevant >> standards prevent us from doing this, e.g. a function that calls >> vprintf will need the macros in , but the C standard >> specifically forbids to include ). > > And in particular, where older POSIX doesn't require the types used in the > function declarations to be defined by a header, but permits them to be > defined by virtue of the general *_t reservation in POSIX (that's not in > ISO C), it's appropriate to define those types whenever declaring > functions that use them, rather than only for the newer POSIX versions > that require those types to be defined alongside declaring the functions > that use them. (So we could simplify some of the conditionals in unistd.h > and remove the "# define uid_t __uid_t" and similar hacks in > conform/data/unistd.h-data, for example.) If you plan to do that (simplify glibc), maybe the changes I'm doing right now may help you. It'll take me a few months to complete, but I plan to further clean the includes in the SYNOPSIS of man[23], so that only the include that provides the prototype is listed, and if any other headers are needed, they'll have an explicit comment about why. After that is merged, you should be able to list all the SYNOPSIS of man[23] (check our for that) and see which specify more than one header (and therefore you'll be able to check if a standard requires it, or if it's a bug in glibc). I'll CC you both when I push those changes. Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/