On 2013-01-15 14:59, Clem Cole wrote:
On Mon, Jan 14, 2013 at 9:21 PM, Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
If there's a PDP-11 PL/I compiler, join me in benchmarking using
some PL/I examples I found on kednos.com <http://kednos.com> ;)
Don't think I've ever seen one. I have F4, F77, Pascal, BASIC+2,
COBOL, BCPL, Simula-2, Xlisp, TECO, Forth... Possibly some other
things that I can't remember now...
Right -- Cutler did the original PL/1 compiler for the VAX only. He
bought the front end from Frieberhouse (aka LPI aka Liant - aka
Ryan-Marfarland). Since it was written in PL/1, Dave had to do the
development at MIT on Multics until it was good enough to could self
host on the VMS. At the time, there was not market need for an PL/1 for
the 11 family and if my memory serves me, I think the development for
the 10's and 20s was going away. PL/1 was IBM's big systems language
and they were trying to move their code base from FORTRAN and Cobol to it,
As for the PDP-11 C compiler generating poor code, that's because it did
not really have too as the feeling was that the Ritchie compiler for
UNIX was not that good either. Any C compiler of the time was viewed as
just needed to work properly, self host and generate correct code. For
the users of DEC OS, folks tended to write in FORTRAN or Macro on the
11s (or BLISS if you were DEC - but you need a 10 to cross compile).
[...]
The PDP-11 C compiler is a much later product than any of the stuff you talk about here. It's something DEC did in the 90s.
As far as I know, Cutler left the PDP-11 scene back in 1974 or so. And while there, he did kernel stuff. He was not involved in any compiler stuff back then as far as I know.
I've never seen the insides of a PL/1 compiler, but I bet it would take some work to get it to fit on a PDP-11... :-)
Johnny
This explanation is insanely helpful! That's what I love about this mailing list.
THanks for the education :)
Ian
On 2013-01-15, at 8:40 AM, "G." <gerry77 at mail.com> wrote:
On Tue, 15 Jan 2013 11:31:53 -0500, you wrote:
How do you replace a symbol with a new one?
IIRC, = with = and == with ==
$ foo == "one"
$ sh sym foo
FOO == "one"
$ foo = "two"
$ sho sym foo
FOO = "two"
$ foo == "three"
$ sho sym foo
FOO = "two"
$ sho sym foo/global
FOO == "three"
i.e. one equal sign is for the local symbol, two equal signs are for the
global symbol, and the local takes precedence over the global.
To delete a symbol: DELETE /SYMBOL
HTH, :)
G.
---
Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=49A249145F3211E2A…
Again bitten by the "do it wrong the first time it fails the second".
:)
-brian
On 1/15/2013 11:35 AM, hvlems at zonnet.nl wrote:
Sorry I put two colons between disk and directory, must be one.
-----Original Message-----
From: Brian Hechinger <wonko at 4amlunch.net>
Sender: owner-hecnet at Update.UU.SE
Date: Tue, 15 Jan 2013 11:27:00
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Ugh
On 1/15/2013 11:19 AM, hvlems at zonnet.nl wrote:
Just a = is enough?
This worked! Now...... why?
Or
$ def/use dcl$path dka0::[bin]
This didn't, however.
-brian
On Tue, 15 Jan 2013 11:31:53 -0500, you wrote:
How do you replace a symbol with a new one?
IIRC, = with = and == with ==
$ foo == "one"
$ sh sym foo
FOO == "one"
$ foo = "two"
$ sho sym foo
FOO = "two"
$ foo == "three"
$ sho sym foo
FOO = "two"
$ sho sym foo/global
FOO == "three"
i.e. one equal sign is for the local symbol, two equal signs are for the
global symbol, and the local takes precedence over the global.
To delete a symbol: DELETE /SYMBOL
HTH, :)
G.
Sorry I put two colons between disk and directory, must be one.
-----Original Message-----
From: Brian Hechinger <wonko at 4amlunch.net>
Sender: owner-hecnet at Update.UU.SE
Date: Tue, 15 Jan 2013 11:27:00
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Ugh
On 1/15/2013 11:19 AM, hvlems at zonnet.nl wrote:
Just a = is enough?
This worked! Now...... why?
Or
$ def/use dcl$path dka0::[bin]
This didn't, however.
-brian
On 1/15/2013 11:29 AM, Stuart Martin wrote:
your original 'SHOW SYM unzip' is showing you that you had previously set up the symbol with a single = and no $
Hmm, so originally I had screwed it up but you can just set it again to overwrite it I guess.
How do you replace a symbol with a new one?
-brian
On 15 January 2013 16:26, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/15/2013 11:23 AM, Mark Wickens wrote:
On 15/01/2013 16:11, Brian Hechinger wrote:
What am I missing here? My VMS is way too rusty.
$ unzip :== $dka0:[bin]unzip_axp.exe
$ unzip
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\DKA0\
$ dir
Directory DKA0:[BIN]
UNZIP_AXP.EXE;1 VIM-73-AXP.ZIP;1
Total of 2 files.
$
-brian
Works OK for me:
[MSW]SLAVE$ unzip :== $dka0:[bin]unzip_axp.exe
[MSW]SLAVE$ show sym unzip
UNZIP == "$DKA0:[BIN]UNZIP_AXP.EXE"
[MSW]SLAVE$
Yeah, symbol assignment works, just not when i try to actually run it:
$ unzip :== $dka0:[bin]unzip_axp.exe
$ show sym unzip
UNZIP = "DKA0:[BIN]UNZIP_AXP.EXE"
$ unzip
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\DKA0\
You don't have a logical name defined for any part of that do you? For example BIN? I once had an issue because I'd defined a drive name logical as DATA which was then being translated. I think that's why using a dollar sign after logical name definitions is good practice for things like drive designators.
no logical named BIN, no.
your original 'SHOW SYM unzip' is showing you that you had previously set up the symbol with a single = and no $
-brian
On 15/01/2013 16:26, Brian Hechinger wrote:
On 1/15/2013 11:23 AM, Mark Wickens wrote:
On 15/01/2013 16:11, Brian Hechinger wrote:
What am I missing here? My VMS is way too rusty.
$ unzip :== $dka0:[bin]unzip_axp.exe
$ unzip
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\DKA0\
$ dir
Directory DKA0:[BIN]
UNZIP_AXP.EXE;1 VIM-73-AXP.ZIP;1
Total of 2 files.
$
-brian
Works OK for me:
[MSW]SLAVE$ unzip :== $dka0:[bin]unzip_axp.exe
[MSW]SLAVE$ show sym unzip
UNZIP == "$DKA0:[BIN]UNZIP_AXP.EXE"
[MSW]SLAVE$
Yeah, symbol assignment works, just not when i try to actually run it:
$ unzip :== $dka0:[bin]unzip_axp.exe
$ show sym unzip
UNZIP = "DKA0:[BIN]UNZIP_AXP.EXE"
$ unzip
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\DKA0\
You don't have a logical name defined for any part of that do you? For example BIN? I once had an issue because I'd defined a drive name logical as DATA which was then being translated. I think that's why using a dollar sign after logical name definitions is good practice for things like drive designators.
no logical named BIN, no.
-brian
Use double quotes around the assignment - for some reason it's not picking up the dollar.
On 1/15/2013 11:19 AM, hvlems at zonnet.nl wrote:
Just a = is enough?
This worked! Now...... why?
Or
$ def/use dcl$path dka0::[bin]
This didn't, however.
-brian
