Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.misc > #11856

Re: SPL/3000 (was Re: Alternatives to C)

From Lars Poulsen <lars@beagle-ears.com>
Newsgroups comp.lang.misc, alt.folklore.computers
Subject Re: SPL/3000 (was Re: Alternatives to C)
Date 2026-08-29 06:14 -0700
Organization A noiseless patient Spider
Message-ID <116ulvj$38h27$1@dont-email.me> (permalink)
References (8 earlier) <rCOMR.3047$_v1.2327@fx21.iad> <87ecfjdr2m.fsf_-_@debian> <dJgkS.592$UGU.176@fx46.iad> <875x0udrqg.fsf@debian> <S9lkS.188322$A8R8.136869@fx35.iad>

Cross-posted to 2 groups.

Show all headers | View raw


On 2026-08-28 12:18, Scott Lurndal wrote:
> Kragen Javier Sitaker <kragen@canonical.org> writes:
...
>> That’s interesting — that wasn’t apparent from the parts of the manul I
>> glanced over.  (I hope that doesn’t sound like I doubt you!)  The HP
>> 3000 didn’t do memory security the way the B5000/B5500 did, did it?
>> With segment descriptors granting fine-grained access to memory, like
>> CHERI today?  I had the impression that it was a relatively conventional
>> 16-bit mini except for having an instruction set that was a more
>> convenient compile target — more like the HP 9825 than like the
>> Burroughs 5500.
...
> 
> SPL/3000 directly exposed the stack to the programmer via the TOS keyword.
> 
> There are a bunch of manuals here:
> 
>     <https://bitsavers.org/pdf/hp/3000/>
> 
> Here's the first part of the SOO application (Son Of Overlord) which monitors system
> utilization (must be run with the capability to access the MCP memory).

Unfortunately, at a cursory glance it seems that the excerpt quoted is 
all comments and declarations, so it does not show anything that turns 
into executable code.

So we have not seen how the language is close to the stack architecture.

-- 
Lars Poulsen - an old geek in Santa Barbara, California

Back to comp.lang.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Alternatives to C (was Re: Safety of casting from 'long' to 'int') cross@spitfire.i.gajendra.net (Dan Cross) - 2026-05-10 13:05 +0000
  Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') Bart <bc@freeuk.com> - 2026-05-12 02:28 +0100
    Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-05-11 18:37 -0700
      Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') Bart <bc@freeuk.com> - 2026-05-12 22:32 +0100
        Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') John Ames <commodorejohn@gmail.com> - 2026-05-12 15:28 -0700
          Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-05-13 02:49 +0200
        Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') scott@slp53.sl.home (Scott Lurndal) - 2026-05-12 23:21 +0000
          Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2026-05-13 02:53 +0200
            Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') scott@slp53.sl.home (Scott Lurndal) - 2026-05-13 14:15 +0000
              Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-05-13 12:30 -0700
                Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') cross@spitfire.i.gajendra.net (Dan Cross) - 2026-05-13 20:20 +0000
          SPL/3000 (was Re: Alternatives to C) Kragen Javier Sitaker <kragen@canonical.org> - 2026-08-27 21:30 -0300
            Re: SPL/3000 (was Re: Alternatives to C) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-28 04:32 +0000
            Re: SPL/3000 (was Re: Alternatives to C) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-28 04:33 +0000
            Re: SPL/3000 (was Re: Alternatives to C) scott@slp53.sl.home (Scott Lurndal) - 2026-08-28 14:14 +0000
              Re: SPL/3000 (was Re: Alternatives to C) Kragen Javier Sitaker <kragen@canonical.org> - 2026-08-28 15:28 -0300
                Re: SPL/3000 (was Re: Alternatives to C) scott@slp53.sl.home (Scott Lurndal) - 2026-08-28 19:18 +0000
                Re: SPL/3000 (was Re: Alternatives to C) Kragen Javier Sitaker <kragen@canonical.org> - 2026-08-28 21:13 -0300
                Re: SPL/3000 (was Re: Alternatives to C) Lars Poulsen <lars@beagle-ears.com> - 2026-08-29 06:14 -0700
                Re: SPL/3000 (was Re: Alternatives to C) Kragen Javier Sitaker <kragen@canonical.org> - 2026-08-29 15:19 -0300
    Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') cross@spitfire.i.gajendra.net (Dan Cross) - 2026-05-12 02:40 +0000
      Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') Bart <bc@freeuk.com> - 2026-05-12 15:11 +0100
    Re: Alternatives to C (was Re: Safety of casting from 'long' to 'int') Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-21 13:59 +0800

csiph-web