From: Stuff Received <stuff@riddermarkfarm.ca>
To: segaloco <segaloco@protonmail.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: Commonality of 60s-80s Print Standards
Date: Thu, 17 Aug 2023 18:52:44 -0400 [thread overview]
Message-ID: <94a15687-0349-c05b-6e5d-7ad6f1d74ab7@riddermarkfarm.ca> (raw)
In-Reply-To: <dfexg5IIDzIjFJGNbICX5_buoybsYrBch09_IgdWD6cpQnakUOJmW1rfpBi9qgAJrnS4SP6JBXvf220JLcVxTSsQ7xJk90KzHTUfnmelDdg=@protonmail.com>
On 2023-08-17 18:11, segaloco via COFF wrote (in part):
> Am I getting into apples vs oranges here?
Yes. In some areas (such as crypto, whence I came), if you did
not follow the standards, then you would not interoperate. There were
no testing labs for compliance (as there was for FIPS, for example).
I recall compliance tests for ANSI C but that stopped with the
adoption of ISO C (if my aging memory is correct).
S.
next prev parent reply other threads:[~2023-08-17 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 15:55 [COFF] " segaloco via COFF
2023-08-17 20:22 ` [COFF] " Paul Winalski
2023-08-17 22:11 ` segaloco via COFF
2023-08-17 22:52 ` Stuff Received [this message]
2023-08-17 23:49 ` segaloco via COFF
2023-08-18 14:07 ` Paul Winalski
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=94a15687-0349-c05b-6e5d-7ad6f1d74ab7@riddermarkfarm.ca \
--to=stuff@riddermarkfarm.ca \
--cc=coff@tuhs.org \
--cc=segaloco@protonmail.com \
/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).