From: arnold@skeeve.com
To: jpl.jpl@gmail.com, arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Speaking commands [Was: Bell System Technical Journal archive]
Date: Wed, 18 Jul 2018 11:39:30 -0600 [thread overview]
Message-ID: <201807181739.w6IHdUZW004045@freefriends.org> (raw)
In-Reply-To: <CAC0cEp9kRS2zVX-o+wpzpQE71-e_wZQLkxA40RPnuuihgC2W7A@mail.gmail.com>
"John P. Linderman" <jpl.jpl@gmail.com> wrote:
> I guess it [ar] lives on in the creation of "libraries" that could be
> loaded by compilers, although I think shared objects have largely replaced
> archive files, and I'm not sure if archive files are even accepted any more.
Archive files (static libraries) are alive and well and work just fine,
on Linux and every other *nix that I know about. The format is even
used on Windows for static libraries and for whatever you call them when
linking dynamic libraries (they provide the symbols, but not the dll).
(Do a file xxx.lib on a Linux system with a .lib file from Windows
and you'll see. Boy was I surprised the first time I did that!)
Arnold
next prev parent reply other threads:[~2018-07-18 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:33 Nemo
2018-07-17 13:20 ` arnold
2018-07-17 14:39 ` John P. Linderman
2018-07-18 17:39 ` arnold [this message]
2018-07-19 4:59 ` [TUHS] ar libraries [was: Speaking commands [Was: Bell System Technical Journal archive]] Greg 'groggy' Lehey
2018-07-19 15:29 ` Paul Winalski
2018-07-19 16:12 ` John P. Linderman
2018-07-20 23:01 ` [TUHS] Speaking commands [Was: Bell System Technical Journal archive] Kurt H Maier
2018-07-18 0:56 ` Ron Natalie
2018-07-18 3:54 ` arnold
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=201807181739.w6IHdUZW004045@freefriends.org \
--to=arnold@skeeve.com \
--cc=jpl.jpl@gmail.com \
--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).