On 7/9/17, ron minnich <rminnich(a)gmail.com> wrote:
>>
> All the DEC-10 and 11 operating systems I used had that wildcard, as well
> as IIRC even the PDP-8, maybe someone can confirm the -8.
>
> It would have been nice had RE's been the standard way to glob files, but,
> that said, when I mention .*\.c to people instead of *.c they don't much
> like it.
So when were REs first designed and implemented? I would imagine that
they came about as a way to extend the old '*' and '?' wildcard
syntax, but that is only a guess.
-Paul W.
> From: Paul Winalski
> So when were REs first designed and implemented? I would imagine that
> they came about as a way to extend the old '*' and '?' wildcard syntax,
> but that is only a guess.
I would suspect in the context of editors, not command file-naming. Don't
have time to research it, though. Try checking CTSS, early Multics, etc.
Noel
Doug McIlroy:
One curious fact is that from day one the word hase been pronounced glob,
not globe. (By contrast, creat has been variously pronounced cree-at
and create.)
=====
On the other hand, the UNIX Room pronunciation of `cron' rhymed with
bone, not with spawn.
Norman Wilson
Toronto ON
> From: Ron Minnich
> Why was it called glob? I always wondered.
Something about global expressions.
I recall reading about this somewhere; I tried looking in the man page:
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V1/man/man7/glob.7
but it didn't go into any detail. I don't know where I could have seen it,
alas...
Noel
Probably no one here wants it, but I have a DR11-W UNIBUS board:
http://bitsavers.trailing-edge.com/pdf/dec/unibus/DR11W_UsersMan.pdf
It's basically a 16-bit DMA interface that can actually do 500Kw per
second (woo hoo! 1MB/sec!) to another DR11-W
Anyone need it? Want it?
Figured I'd try here first, in case we had some historic UNIX people
that were still running a UNIBUS PDP-11 (or VAX).
No takers in a few weeks, I'll try the museums next.
thanks
art k.
> From: Toby Thain
> Are we to infer that neither Noel and Clem are "good homes"?
Well, I said something like 'I don't have an immediate need for it, but I'd
be happy to take it', so I guess the question is 'does someone have an
actual, immediate use for it' (which I don't)?
Noel
Does anyone here remember the Adventure Shell?
Doug wrote it back in 83, and I just stumbled across a copy in an RCS directory.
Invoked as ‘ash’ it was pretty clever. I’ve lost the instructions and help files, however I’ve got the main script.
Back when people did weird things because it was fun.
David
> Browsing the source for "cc" in v6 and v7, if invoked with -2 would
> replace crt0.o with crt2.o. If the -2 were followed by another character
> (probably intended to be -20), it would use crt20.o and use -l2 instead
> of -lc.
>
> These options seem to be undocumented, and I can't find any source code
> of these libraries or indication as to what the purpose was.
The "scc" man page for System V may be enlightening, as it mentions
similarly-named files:
NAME
scc - C compiler for stand-alone programs
SYNOPSIS
scc [ +[ lib ] ] [ option ] ... [ file ] ...
DESCRIPTION
Scc prepares the named files for stand-alone execution.
[...]
FILES
/lib/crt2.o execution start-off
/usr/lib/lib2.a stand-alone library
/usr/lib/lib2A.a +A configuration library
/usr/lib/lib2B.a +B configuration library
-- Richard
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
Hi,
two remarks on the issues around FPSIM and tcsh:
I of course wondered by a line like
mov $4..,r0
is accepted by 'as', I naively expected that this should cause an error.
I didn't locate the 211bsd 'as' manual, so checked 7th Edition manuals,
which can be found under
https://wolfram.schneider.org/bsd/7thEdManVol2/
The assembler manual, see
https://wolfram.schneider.org/bsd/7thEdManVol2/assembler/assembler.pdf
states
6.1 Expression operators
The operators are:
(blank) when there is no operand between operands,
the effect is exactly the same as if a
‘+’ had appeared.
So the lexer sees two tokens
$4. --> number
. --> symbol for location counter
and, because the default operator is '+', interprets this as
mov $4. + . , r0
which ends up being a number in the 160000 to 177777 range.
So 'as' is not to blame, works as designed.
Noel Chippa wrote:
> I'm fairly amazed that apparently nobody has run across one of these 4 before!
> (Or, at least, not bothered to report it.)
> I wonder how long that bug has been in the code?
The answer is: this bug was in 211bsd all the time.
Steven Schultz told me that that they simply didn't have a way to
test FPSIM because all machines had FPP, and the only way of testing
would have been to physically remove the FP11 from a 11/70.
With best regards, Walter