From: James Johnston <audioskeptic@gmail.com>
To: Stuff Received <stuff@riddermarkfarm.ca>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: ANSI (C) vs IEEE (POSIX) Standards Body Selection
Date: Wed, 26 Jun 2024 15:33:51 -0700 [thread overview]
Message-ID: <CAO2qRdNBGJrBeWMjYhZTYuASMf=VyAiwT0kkZ48Y_s9bn5emJg@mail.gmail.com> (raw)
In-Reply-To: <e88f6be8-7bcd-83c8-90fa-f2e88307286f@riddermarkfarm.ca>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Strictly speaking ANSI would assign a Joint Technical Committee (JTC) who
would assign or create a Subcommittee, who would would then create a
working group responsible for conformance testing.
Don't ask why I know all this.
On Wed, Jun 26, 2024 at 3:32 PM Stuff Received <stuff@riddermarkfarm.ca>
wrote:
> On 2024-06-26 14:35, Marc Rochkind wrote (in part):
> > I think historically ANSI did languages.
>
> Once upon a time, ANSI even had conformance testing (though that is not
> really relevant to this thread #6-).
>
> S.
>
--
James D. (jj) Johnston
Chief Scientist, Immersion Networks
[-- Attachment #2: Type: text/html, Size: 1119 bytes --]
next prev parent reply other threads:[~2024-06-26 22:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 17:56 [TUHS] " segaloco via TUHS
2024-06-26 18:32 ` [TUHS] " Ori Idan
2024-06-26 18:42 ` Marc Rochkind
2024-06-26 20:07 ` Aron Insinga
2024-06-26 23:28 ` Peter Yardley
2024-06-26 18:35 ` Marc Rochkind
2024-06-26 18:43 ` James Johnston
2024-06-26 18:52 ` segaloco via TUHS
2024-06-26 19:34 ` Heinz Lycklama
2024-06-26 20:01 ` Charles H Sauer (he/him)
2024-06-27 2:36 ` [TUHS] Re: arithmetic, " John Levine
2024-06-27 3:41 ` Charles H. Sauer
2024-06-26 20:29 ` [TUHS] " Marc Rochkind
2024-06-26 21:17 ` Rich Salz
2024-06-26 21:20 ` Alan Coopersmith via TUHS
2024-06-26 21:28 ` Warner Losh
2024-06-26 21:49 ` Rich Salz
2024-06-26 21:53 ` Steffen Nurpmeso
2024-06-27 0:44 ` Clem Cole
2024-06-27 1:11 ` [TUHS] Origin of the name POSIX (was: ANSI (C) vs IEEE (POSIX) Standards Body Selection) Greg 'groggy' Lehey
2024-06-27 2:12 ` [TUHS] " Ron Natalie
2024-06-27 2:37 ` Warner Losh
2024-06-27 14:19 ` Steffen Nurpmeso
[not found] ` <CAC20D2M+75ohjTPcTBmBkejeaWjQQjWCkf=4ZYrP4Bk0MCamKA@mail.gmail.com>
2024-06-27 3:02 ` Clem Cole
2024-06-27 3:03 ` Clem Cole
2024-06-27 3:08 ` Clem Cole
2024-06-27 8:20 ` Eric E. Bowles via TUHS
2024-06-27 11:56 ` John S Quarterman
[not found] ` <CAEoi9W4ZSVCVsJJ8pdBuBobeeXOkwsey0kM6DWBnPiuSd_7TQA@mail.gmail.com>
[not found] ` <CANCZdfoghuf4n=HDgRJXDJ5VqZ=rCtmq_0WadaR6kj8QmcoVQQ@mail.gmail.com>
2024-06-27 13:42 ` John S Quarterman
2024-06-27 11:58 ` Dan Cross
2024-06-27 14:34 ` Clem Cole
2024-06-27 15:05 ` [TUHS] Re: Origin of the name POSIX Heinz Lycklama
2024-06-27 13:57 ` [TUHS] Re: ANSI (C) vs IEEE (POSIX) Standards Body Selection Steffen Nurpmeso
2024-06-27 14:22 ` Chet Ramey via TUHS
2024-06-27 14:29 ` Andy Kosela
2024-06-27 14:59 ` Clem Cole
2024-06-27 4:12 ` Wesley Parish
2024-06-27 4:52 ` G. Branden Robinson
2024-06-26 19:47 ` Aron Insinga
2024-06-27 5:02 ` Nevin Liber
2024-06-26 20:36 ` Stuff Received
2024-06-26 22:33 ` James Johnston [this message]
2024-06-26 20:32 ` Clem Cole
2024-06-26 22:04 ` Heinz Lycklama
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='CAO2qRdNBGJrBeWMjYhZTYuASMf=VyAiwT0kkZ48Y_s9bn5emJg@mail.gmail.com' \
--to=audioskeptic@gmail.com \
--cc=stuff@riddermarkfarm.ca \
--cc=tuhs@tuhs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).