All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Matt Jolly <Matt.Jolly@footclan.ninja>, linux-man@vger.kernel.org
Subject: Re: Revert "Many Pages: Remove references to C89"
Date: Fri, 10 Mar 2023 03:22:12 +0100	[thread overview]
Message-ID: <8899aff7-4193-dd54-4488-234b1a6cee83@gmail.com> (raw)
In-Reply-To: <20230310015150.3545768-1-Matt.Jolly@footclan.ninja>


[-- Attachment #1.1: Type: text/plain, Size: 2328 bytes --]

Hi Matt,

On 3/10/23 02:51, Matt Jolly wrote:
> Hi All
> 
> I hope this email finds you well. I am writing to raise an issue that has been causing inconvenience
> for me (and potentially others). The recent removal of C89 information from man pages
> (72b349dd8c209d7375d4d4f76e2315943d654ee9) has put me in a difficult situation.
> As I continue to work on code that adheres to the C89 style, such as cURL, I am unable to quickly
> determine if a particular function can be used or if it was introduced in a later standard like C99.
> This slows down my workflow and hampers my productivity.
> 
> Therefore, I kindly request that we revert the changes made in the "Many pages: Remove references to C89" patch.
> Furthermore, I urge everyone to recognize the importance of this information and ensure it is not removed from man pages in the future.

The main problem was that the existing info about C89 was not consistent.
Some pages declared APIs being standard since C89, while others didn't.
Incorrect info isn't much better than no info.

I'm curious about cURL's real need for C89.  I see that cURL uses GNU
extensions (-std=gnu89), which actually pulls most of C99[1] (I think
it pulls the entire C library, and most of the core language).

Virtually all (even MS, which has always been the last in this)
systems support C99; why would you consciously avoid it?  Is there
any system that doesn't yet support it?  Which are the C libraries
that you need to support that don't provide C99 functions by default
(or at all)?

I'd like to really understand the need for C89 in 2023.


Cheers,

Alex


> 
> Thank you for your attention to this matter. Please let me know if you have any questions or concerns.
> 
> Cheers,
> 
> Matt
> 
> 


[1]:

$ cat llabs.c 
#include <stdlib.h>

int f(void)
{
	return llabs(0);
}


$ cc -Wall -Wextra -std=c89 llabs.c -S
llabs.c: In function ‘f’:
llabs.c:5:16: warning: implicit declaration of function ‘llabs’; did you mean ‘labs’? [-Wimplicit-function-declaration]
    5 |         return llabs(0);
      |                ^~~~~
      |                labs


$ cc -Wall -Wextra -std=gnu89 llabs.c -S
$


-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-03-10  2:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  1:51 Revert "Many Pages: Remove references to C89" Matt Jolly
2023-03-10  1:51 ` [PATCH] Revert "Many pages: " Matt Jolly
2023-03-10  2:22 ` Alejandro Colomar [this message]
2023-03-10  5:00   ` Revert "Many Pages: " Oskari Pirhonen
2023-03-10 13:29     ` Alejandro Colomar
2023-03-10 13:32       ` Alejandro Colomar
2023-03-13  1:42       ` Oskari Pirhonen
2023-03-13 12:00         ` Alejandro Colomar
2023-03-14  5:39           ` Oskari Pirhonen
2023-03-15 12:30             ` Alejandro Colomar
2023-03-15 12:53               ` Alejandro Colomar
2023-03-15 12:54                 ` Alejandro Colomar
2023-03-15 14:22                 ` Alejandro Colomar
2023-03-15 16:51               ` Brian Inglis
2023-03-15 17:01                 ` Alejandro Colomar
2023-03-15 18:10                   ` Tom Schwindl
2023-03-16  1:43                     ` Alejandro Colomar
2023-03-18  4:58                       ` Oskari Pirhonen
2023-03-22  1:20                         ` Alejandro Colomar
2023-03-15  4:36           ` Guillem Jover
2023-03-10  6:40   ` Brian Inglis
2023-03-10 12:49     ` Alejandro Colomar
2023-03-23  5:32   ` Sam James
2023-03-23 13:13     ` Alejandro Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8899aff7-4193-dd54-4488-234b1a6cee83@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=Matt.Jolly@footclan.ninja \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.