tech@mandoc.bsd.lv
 help / color / Atom feed
* [PATCH] Add POSIX.1-2017 to St macro
@ 2020-03-04  2:16 Michael Forney
  2020-03-04  2:56 ` Ingo Schwarze
  0 siblings, 1 reply; 4+ messages in thread
From: Michael Forney @ 2020-03-04  2:16 UTC (permalink / raw)
  To: tech

Index: st.c
===================================================================
RCS file: /cvs/mandoc/st.c,v
retrieving revision 1.16
diff -u -r1.16 st.c
--- st.c	14 Dec 2018 01:18:26 -0000	1.16
+++ st.c	4 Mar 2020 01:56:06 -0000
@@ -37,6 +37,7 @@
 LINE("-p1003.1-2001",	"IEEE Std 1003.1-2001 (\\(lqPOSIX.1\\(rq)")
 LINE("-p1003.1-2004",	"IEEE Std 1003.1-2004 (\\(lqPOSIX.1\\(rq)")
 LINE("-p1003.1-2008",	"IEEE Std 1003.1-2008 (\\(lqPOSIX.1\\(rq)")
+LINE("-p1003.1-2017",	"IEEE Std 1003.1-2017 (\\(lqPOSIX.1\\(rq)")
 LINE("-p1003.1",	"IEEE Std 1003.1 (\\(lqPOSIX.1\\(rq)")
 LINE("-p1003.1b",	"IEEE Std 1003.1b (\\(lqPOSIX.1b\\(rq)")
 LINE("-p1003.1b-93",	"IEEE Std 1003.1b-1993 (\\(lqPOSIX.1b\\(rq)")
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] Add POSIX.1-2017 to St macro
  2020-03-04  2:16 [PATCH] Add POSIX.1-2017 to St macro Michael Forney
@ 2020-03-04  2:56 ` Ingo Schwarze
  2020-03-04  3:50   ` Michael Forney
  0 siblings, 1 reply; 4+ messages in thread
From: Ingo Schwarze @ 2020-03-04  2:56 UTC (permalink / raw)
  To: Michael Forney; +Cc: tech

Hi Michael,

Michael Forney wrote on Tue, Mar 03, 2020 at 06:16:44PM -0800:

> Index: st.c
> ===================================================================
> RCS file: /cvs/mandoc/st.c,v
> retrieving revision 1.16
> diff -u -r1.16 st.c
> --- st.c	14 Dec 2018 01:18:26 -0000	1.16
> +++ st.c	4 Mar 2020 01:56:06 -0000
> @@ -37,6 +37,7 @@
>  LINE("-p1003.1-2001",	"IEEE Std 1003.1-2001 (\\(lqPOSIX.1\\(rq)")
>  LINE("-p1003.1-2004",	"IEEE Std 1003.1-2004 (\\(lqPOSIX.1\\(rq)")
>  LINE("-p1003.1-2008",	"IEEE Std 1003.1-2008 (\\(lqPOSIX.1\\(rq)")
> +LINE("-p1003.1-2017",	"IEEE Std 1003.1-2017 (\\(lqPOSIX.1\\(rq)")
>  LINE("-p1003.1",	"IEEE Std 1003.1 (\\(lqPOSIX.1\\(rq)")
>  LINE("-p1003.1b",	"IEEE Std 1003.1b (\\(lqPOSIX.1b\\(rq)")
>  LINE("-p1003.1b-93",	"IEEE Std 1003.1b-1993 (\\(lqPOSIX.1b\\(rq)")

No, absolutely not.  That is not a new version of POSIX, it is
merely the incorporation of a technical corrigendum.  Manual pages
ought to continue referncing -p1003.1-2008.

In those very rare cases where the TC might require code changes,
those code changes can usually be considered bug fixes but do not
change how the related features are supposed to work and how they
need to be documented.

Even if a handful of manual pages need to reference the TC, for
example to make it explicit that the program in questions conforms
to some changed behaviour required by the TC, that doesn't require
a dedicated macro.  Such an unusual case ought to be described more
explicitly if it really matters and not only by changing a number
that most readers will almost certainly overlook.  And i haven't
even seen a single example yet where discussing the TC in a manual
page might be required...

Besides, this has already been discussed repeatedly.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] Add POSIX.1-2017 to St macro
  2020-03-04  2:56 ` Ingo Schwarze
@ 2020-03-04  3:50   ` Michael Forney
  2020-03-16 10:01     ` Ingo Schwarze
  0 siblings, 1 reply; 4+ messages in thread
From: Michael Forney @ 2020-03-04  3:50 UTC (permalink / raw)
  To: Ingo Schwarze; +Cc: tech

On 2020-03-03, Ingo Schwarze <schwarze@usta.de> wrote:
> No, absolutely not.  That is not a new version of POSIX, it is
> merely the incorporation of a technical corrigendum.  Manual pages
> ought to continue referncing -p1003.1-2008.

I'm aware that it's just a bug fix release, but it is a version of the
standard nonetheless, so I thought it would be useful to be able to
refer to it.

IEEE Std 1003.1-2004 is also just the incorporation of a couple TCs
into 1003.1-2001, yet it is supported by mandoc. I don't really see
the difference between that case and 1003.1-2017.

> Besides, this has already been discussed repeatedly.

Sorry about that, I didn't know this had already been discussed (I
wasn't able to find any mailing list archives).

-Michael
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] Add POSIX.1-2017 to St macro
  2020-03-04  3:50   ` Michael Forney
@ 2020-03-16 10:01     ` Ingo Schwarze
  0 siblings, 0 replies; 4+ messages in thread
From: Ingo Schwarze @ 2020-03-16 10:01 UTC (permalink / raw)
  To: Michael Forney; +Cc: tech

Hi Michael,

Michael Forney wrote on Tue, Mar 03, 2020 at 07:50:52PM -0800:
> On 2020-03-03, Ingo Schwarze <schwarze@usta.de> wrote:

>> No, absolutely not.  That is not a new version of POSIX, it is
>> merely the incorporation of a technical corrigendum.  Manual pages
>> ought to continue referncing -p1003.1-2008.

> I'm aware that it's just a bug fix release, but it is a version of the
> standard nonetheless, so I thought it would be useful to be able to
> refer to it.
> 
> IEEE Std 1003.1-2004 is also just the incorporation of a couple TCs
> into 1003.1-2001, yet it is supported by mandoc. I don't really see
> the difference between that case and 1003.1-2017.

It is harder to undo errors made in the past than to avoid similar
errors in the future.

It would be good to delete .St -p1003.1-2004, but that would require
hunting down the instances where it is used in all the BSD systems
first.  For example, in OpenBSD, it is still used in six pages,
and it is used by mistake in every single case.

In FreeBSD, it is used about 30 times, in NetBSD about 80 times.
And then there are DragonFly and illumos.
Doing that work such that it can be cleaned up is not high priority.

>> Besides, this has already been discussed repeatedly.

> Sorry about that, I didn't know this had already been discussed (I
> wasn't able to find any mailing list archives).

I tried to get the mandoc lists into marc.info, but never got a response
from the maintainers of that service, and i never came round to set up
my own web archive.  It would certainly be useful.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-04  2:16 [PATCH] Add POSIX.1-2017 to St macro Michael Forney
2020-03-04  2:56 ` Ingo Schwarze
2020-03-04  3:50   ` Michael Forney
2020-03-16 10:01     ` Ingo Schwarze

tech@mandoc.bsd.lv

Archives are clonable: git clone --mirror http://inbox.vuxu.org/mandoc-tech

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.mandoc.tech


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git