All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: linux-man@vger.kernel.org
Subject: Re: Revert "Many Pages: Remove references to C89"
Date: Wed, 15 Mar 2023 18:01:22 +0100	[thread overview]
Message-ID: <a1a5ea63-9fbe-17f6-fe69-1850552a5422@gmail.com> (raw)
In-Reply-To: <6aad40b5-04ca-68d8-7da2-cb4a7bed7ded@Shaw.ca>

Hi Brian,

On 3/15/23 17:51, Brian Inglis wrote:
> On 2023-03-15 06:30, Alejandro Colomar wrote:
>> On 3/14/23 06:39, Oskari Pirhonen wrote:
>>> On Mon, Mar 13, 2023 at 13:00:52 +0100, Alejandro Colomar wrote:
>>>>>> <https://port70.net/~nsz/c/c89/c89-draft.txt>
>>>>>> I suggest you download that file, and use a function like this:
>>>>>> $ stdc89() { grep "[[:alpha:]] \**\b$1([[:alnum:]*,. ]*);" /path/to/c89-draft.txt; }
>>>>>> $ stdc89 printf
>>>>>>           int printf(const char *format, ...);
>>>>>>           int printf(const char *format, ...);
> 
>>>>> I gave this a quick spin and it seems to work decently well. So thanks
>>>>> for that.
> 
>>>>> It's still not quite as nice as having C89 mentioned in
>>>>> STANDARDS, and couldn't this be leveraged to fix up the inconsistencies
>>>>> you mentioned earlier?
> 
>>> Looking at the site you linked to for the c89-draft.txt, there's also
>>> C99, C11, and C2x. With yet some more work, it'd be possible to have
>>> equivalent functions for those standards as well. They could even be
>>> combined to create an "std-diff" tool to give, eg, new "str*" functions
>>> introduced in C89 -> C99.
>>> Perhaps such a tool already exists, but I thought it worth mentioning
>>> here in case anyone reading this gets inspired to write it. I've added
>>> it to my (ever growing) TODO list, but don't know when I might get
>>> around to actually giving it a go.
> 
>> Interesting idea.  Sounds fun to do.  I'll check if we can redistribute
>> the drafts of the standard in the Linux man-pages repo.  If so, we could
>> have the standard .txt files in some directory inside the repo, and then
>> have a script that reads those files.
> 
> I have an archive of many drafts including (so far):
> 
>   1.5M Sep 10  1998 N0843-C1999-CD-1998-08.pdf
>   3.4M May  6  2005 N1124-C1999+TC2-CD-2005-05.pdf
>   3.7M Sep  8  2007 N1256-C1999+TC3-CD-2007-09.pdf
>   1.7M Apr 12  2011 N1570-C201X-CD-2011-04.pdf
>   2.3M Oct  9  2017 N2176-C2017-CD-2017-10.pdf
>   6.7M Jan 24 11:37 N3088-C2023-CD1-2023-01.pdf
> 
> which can be downloaded as:
> 
> 	https://www.open-std.org/jtc1/sc22/wg14/www/docs/n####.pdf

Do you know if we can distribute them?  which license applied to them?
I'm worried that some distros are very strict in what can be distributed
in a package (e.g., Fedora, Debian (main)).  There were issues with
man-pages-posix in the past.

Should we maybe open a separate project iso-c-drafts that installs
drafts of the ISO C standards and maybe some scripts that will be useful
with them?


> 
> Package poppler contains pdftotext which with -layout produces easily searchable 
> text files.

Nice.


Thanks,

Alex

  reply	other threads:[~2023-03-15 17:01 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 ` Revert "Many Pages: " Alejandro Colomar
2023-03-10  5:00   ` 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 [this message]
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=a1a5ea63-9fbe-17f6-fe69-1850552a5422@gmail.com \
    --to=alx.manpages@gmail.com \
    --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.