From: charles.unix.pro@gmail.com (Charles Anthony)
Subject: [TUHS] Dash options
Date: Tue, 28 Nov 2017 18:22:37 -0800 [thread overview]
Message-ID: <CANV78LTMtdogV54MimCB3dsrSCG_z9H6ciG=7M8h1ERaTWrDrg@mail.gmail.com> (raw)
In-Reply-To: <201711290123.vAT1NfXT028532@coolidge.cs.Dartmouth.EDU>
On Tue, Nov 28, 2017 at 5:23 PM, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
> Early on, when multics was understood to have
> one big, segemented address space, it was expected
> that PL/I name qualification ($) would serve to address
> segments. I do not know whether that idea was
> actually implemented.
>
>
If I understand you correctly, approximately yes.
Entry points are usually defined as "foo$bar", where "foo" is the segment
name, and "bar" an entry point in the segment symbol table. I believe that
the degerate case of "foo$" is treated as "foo$foo" by the shell.
In the following example, the segment name is "hello", the entry point
"world".
*edm hello.pl1*
Segment not found.
Input.
*world: procedure options(main);*
* dcl sysprint file output print stream;*
* put list ("Multics rulez; UNIX droolz");*
* put skip;*
*end world;*
*.*
Edit.
*w*
*q*
r 16:45 0.050 3
*pl1 hello*
PL/1 33e
r 16:45 0.128 36
*hello$world*
Multics rulez; UNIX droolz
r 16:45 0.033 23
-- Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171128/51493d01/attachment.html>
next prev parent reply other threads:[~2017-11-29 2:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 1:23 Doug McIlroy
2017-11-29 1:37 ` George Michaelson
2017-11-29 2:22 ` Charles Anthony [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-29 14:03 Noel Chiappa
2017-11-29 20:29 ` Charles Anthony
[not found] <mailman.376.1511899437.9955.tuhs@minnie.tuhs.org>
2017-11-28 21:30 ` Paul Ruizendaal
2017-11-28 13:19 Noel Chiappa
2017-11-28 18:20 ` Clem Cole
2017-11-28 21:56 ` Dave Horsfall
2017-11-28 5:51 Jon Steinhart
2017-11-28 6:05 ` Dave Horsfall
2017-11-28 6:49 ` Andrew Warkentin
2017-11-28 11:18 ` Ralph Corderoy
2017-11-28 11:49 ` Michael Kjörling
2017-11-28 12:46 ` Ralph Corderoy
2017-11-28 18:01 ` Lawrence Stewart
2017-11-28 19:36 ` Paul Winalski
2017-11-28 20:03 ` Clem Cole
2017-11-28 6:28 ` Greg 'groggy' Lehey
2017-11-29 19:16 ` Steffen Nurpmeso
[not found] ` <20171204054651.GA17671@eureka.lemis.com>
[not found] ` <20171204215701.l9Pvr%steffen@sdaoden.eu>
2017-12-05 13:22 ` Steffen Nurpmeso
2017-12-07 5:15 ` Greg 'groggy' Lehey
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='CANV78LTMtdogV54MimCB3dsrSCG_z9H6ciG=7M8h1ERaTWrDrg@mail.gmail.com' \
--to=charles.unix.pro@gmail.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).