On 10/05/2026 05:39, Janis Papanagnou wrote:
[snip]
What makes you think that I'd need to write an own language given that
there's a plethora of languages of all kinds and paradigms existing.
So where's the one that works like mine?
And why are there so many new ones still appearing? Most of them you
will not know about.
In article <10tpt9j$c3i4$1@dont-email.me>, Bart <bc@freeuk.com> wrote:
On 10/05/2026 05:39, Janis Papanagnou wrote:
[snip]
What makes you think that I'd need to write an own language given that
there's a plethora of languages of all kinds and paradigms existing.
So where's the one that works like mine?
I mean, Rust does exactly what you were just describing.
And why are there so many new ones still appearing? Most of them you
will not know about.
Consider the possibility that you may be unique in the world in
possessing the combination of requirements and aesthetic
judgement that makes you feel you need a language like yours.
As for new languages, there are a number of reasons. Most of
them are not particularly relevant here.
At this point, you may consider doing what Keith suggested, and
moving further discussion of your language to comp.lang.misc.
I don't have much of a problem with the things that C can do, but with
how it does it, its syntax, its ancient baggage, its quirks, its
folklore, its Unix-centric ecosystem, its pointless UBs, its
insistence in working with every oddball processor, its solving every shortcoming with macros, its adherents who will defend every
misfeature to the death...
It is also frustrating looking at C forums and people thinking they
are too stupid to grasp something when it's language that could have
been better.
On 10/05/2026 14:05, Dan Cross wrote:
In article <10tpt9j$c3i4$1@dont-email.me>, Bart <bc@freeuk.com> wrote:
On 10/05/2026 05:39, Janis Papanagnou wrote:
[snip]
What makes you think that I'd need to write an own language given that >>>> there's a plethora of languages of all kinds and paradigms existing.
So where's the one that works like mine?
I mean, Rust does exactly what you were just describing.
Rust could hardly be more different than mine.
And why are there so many new ones still appearing? Most of them you
will not know about.
Consider the possibility that you may be unique in the world in
possessing the combination of requirements and aesthetic
judgement that makes you feel you need a language like yours.
My language fills the same niche that C does.
I don't have much of a problem with the things that C can do, but with
how it does it, its syntax, its ancient baggage, its quirks, its
folklore, its Unix-centric ecosystem, its pointless UBs, its insistence
in working with every oddball processor, its solving every shortcoming
with macros, its adherents who will defend every misfeature to the death...
Maybe the answer is to just create my own language?! I did exactly that,
and didn't to have to deal with C for 10-15 years, but you can't get
away from it because it's everywhere.
It is also frustrating looking at C forums and people thinking they are
too stupid to grasp something when it's language that could have been >better.
As for new languages, there are a number of reasons. Most of
them are not particularly relevant here.
At this point, you may consider doing what Keith suggested, and
moving further discussion of your language to comp.lang.misc.
Sure, a pretty much dead group.
In article <10ttvng$1j579$1@dont-email.me>, Bart <bc@freeuk.com> wrote:
On 10/05/2026 14:05, Dan Cross wrote:
In article <10tpt9j$c3i4$1@dont-email.me>, Bart <bc@freeuk.com> wrote: >>>> On 10/05/2026 05:39, Janis Papanagnou wrote:
[snip]
What makes you think that I'd need to write an own language given that >>>>> there's a plethora of languages of all kinds and paradigms existing.
So where's the one that works like mine?
I mean, Rust does exactly what you were just describing.
Rust could hardly be more different than mine.
You were describing what Rust calls, `include_str!` and
`include_bytes!`. That's what I was referring to.
https://doc.rust-lang.org/std/macro.include_str.html https://doc.rust-lang.org/std/macro.include_bytes.html
It is also frustrating looking at C forums and people thinking they are
too stupid to grasp something when it's language that could have been
better.
The problem you keep encountering here, specifically, is that by
your own admission you do not know C, the language, well enough
to accurately understand what would have made it a "language
that could have been better."
Bart <bc@freeuk.com> writes:
[...]
I don't have much of a problem with the things that C can do, but with
how it does it, its syntax, its ancient baggage, its quirks, its
folklore, its Unix-centric ecosystem, its pointless UBs, its
insistence in working with every oddball processor, its solving every
shortcoming with macros, its adherents who will defend every
misfeature to the death...
You're mostly wrong about that last point. Many of us spend a
great deal of time and effort here *explaining* how C is defined
and how best to use it.
To explain is not to defend. What will it take for you to understand
that?
[...]
It is also frustrating looking at C forums and people thinking they
are too stupid to grasp something when it's language that could have
been better.
(I'm going to assume I parsed that sentence correctly.)
Nobody has said that C couldn't have been better. But it could
hardly have been more successful. As Dennis Ritchie himself said,
"C is quirky, flawed, and an enormous success."
[...]
Even half a century ago, there were big companies and lots of cleverI am reminded of Seymour Cray's rebuttal to Tom Watson:
people, who could have cranked out a suitable systems language of
equal capability to C in their sleep, but with fewer rough edges.
I wonder why they didn't?
On 12/05/2026 02:37, Keith Thompson wrote:<snip>
Bart <bc@freeuk.com> writes:
[...]
Nobody has said that C couldn't have been better. But it could
hardly have been more successful. As Dennis Ritchie himself said,
"C is quirky, flawed, and an enormous success."
Yeah, it's one of the great mysteries. Even half a century ago, there
were big companies and lots of clever people, who could have cranked out
a suitable systems language of equal capability to C in their sleep, but >with fewer rough edges.
On Tue, 12 May 2026 22:32:30 +0100
Bart <bc@freeuk.com> wrote:
Even half a century ago, there were big companies and lots of clever
people, who could have cranked out a suitable systems language of
equal capability to C in their sleep, but with fewer rough edges.
I wonder why they didn't?
I am reminded of Seymour Cray's rebuttal to Tom Watson:
"I understand that in the laboratory developing this system there are
only 34 people, 'including the janitor.' Of these, 14 are engineers and
4 are programmers, and only one has a Ph. D., a relatively junior
programmer. To the outsider, the laboratory appeared to be cost
conscious, hard working and highly motivated.
Contrasting this modest effort with our own vast development
activities, I fail to understand why we have lost our industry
leadership position by letting someone else offer the worldrCOs most
powerful computer."
"It seems like Mr. Watson has answered his own question."
Bart <bc@freeuk.com> writes:
On 12/05/2026 02:37, Keith Thompson wrote:
[...]
Yeah, it's one of the great mysteries. Even half a century ago, there
were big companies and lots of clever people, who could have cranked out
a suitable systems language of equal capability to C in their sleep, but
with fewer rough edges.
Those clever people _were_ cranking out suitable systems languages
by the bucketful. PL/1, Algol derivatives, proprietary internal
languages (Burroughs SPRITE and BPL languages), HP-3000 SPL (Systems Programming Language - I used SPL in the late 70s) and
on the academic side, modula, ADA, Pascal (yes, it could be
a systems programming language, c.f. VAX-11 Pascal).
[...]
On 2026-05-13 01:21, Scott Lurndal wrote:
Bart <bc@freeuk.com> writes:
On 12/05/2026 02:37, Keith Thompson wrote:
[...]
Yeah, it's one of the great mysteries. Even half a century ago, there
were big companies and lots of clever people, who could have cranked out >>> a suitable systems language of equal capability to C in their sleep, but >>> with fewer rough edges.
Those clever people _were_ cranking out suitable systems languages
by the bucketful. PL/1, Algol derivatives, proprietary internal
languages (Burroughs SPRITE and BPL languages), HP-3000 SPL (Systems
Programming Language - I used SPL in the late 70s) and
on the academic side, modula, ADA, Pascal (yes, it could be
a systems programming language, c.f. VAX-11 Pascal).
[...]
I wonder about why you put Ada just in the "academic box".
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:[...]
I wonder about why you put Ada just in the "academic box".
Because the first ADA compiler I used came from NYU. :-)
scott@slp53.sl.home (Scott Lurndal) writes:
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:[...]
I wonder about why you put Ada just in the "academic box".
Because the first ADA compiler I used came from NYU. :-)
It's Ada, not ADA. It's a person's name, not an acronym.
On 10/05/2026 14:05, Dan Cross wrote:
In article <10tpt9j$c3i4$1@dont-email.me>, Bart-a <bc@freeuk.com> wrote:
On 10/05/2026 05:39, Janis Papanagnou wrote:
[snip]
What makes you think that I'd need to write an own language given that >>>> there's a plethora of languages of all kinds and paradigms existing.
So where's the one that works like mine?
I mean, Rust does exactly what you were just describing.
Rust could hardly be more different than mine.
And why are there so many new ones still appearing? Most of them you
will not know about.
Consider the possibility that you may be unique in the world in
possessing the combination of requirements and aesthetic
judgement that makes you feel you need a language like yours.
My language fills the same niche that C does.
I don't have much of a problem with the things that C can do, but with
how it does it, its syntax, its ancient baggage, its quirks, its
folklore, its Unix-centric ecosystem, its pointless UBs, its insistence
in working with every oddball processor, its solving every shortcoming
with macros, its adherents who will defend every misfeature to the death...
Maybe the answer is to just create my own language?! I did exactly that,
and didn't to have to deal with C for 10-15 years, but you can't get
away from it because it's everywhere.
It is also frustrating looking at C forums and people thinking they are
too stupid to grasp something when it's language that could have been better.
As for new languages, there are a number of reasons.-a Most of
them are not particularly relevant here.
At this point, you may consider doing what Keith suggested, and
moving further discussion of your language to comp.lang.misc.
Sure, a pretty much dead group.
Those clever people _were_ cranking out suitable systems languages by
the bucketful. (...), HP-3000 SPL (Systems Programming Language - I
used SPL in the late 70s)
IrCOm interested to hear how SPL compared to C and Pascal from your perspective. IrCOve never talked to anyone who had the chance to use
it. Glancing at <http://bitsavers.informatik.uni-stuttgart.de/pdf/hp/3000/spl/30000-90025_System_Programming_Language_Textbook_197709.pdf#page=124>
it looks pretty similar to themrCerCorCea bit longer-winded and SHOUTIER
than C, a bit more practical than Pascal, but showing a very strong
family resemblance to both.
IrCOm interested to hear how SPL compared to C and Pascal from your perspective. IrCOve never talked to anyone who had the chance to use
it. Glancing at <http://bitsavers.informatik.uni-stuttgart.de/pdf/hp/3000/spl/30000-90025_System_Programming_Language_Textbook_197709.pdf#page=124>
it looks pretty similar to themrCerCorCea bit longer-winded and SHOUTIER
than C, a bit more practical than Pascal, but showing a very strong
family resemblance to both.
scott@slp53.sl.home (Scott Lurndal) writes:
Those clever people _were_ cranking out suitable systems languages by
the bucketful. (...), HP-3000 SPL (Systems Programming Language - I
used SPL in the late 70s)
IrCOm interested to hear how SPL compared to C and Pascal from your >perspective. IrCOve never talked to anyone who had the chance to use it.
scott@slp53.sl.home (Scott Lurndal) writes:
Kragen Javier Sitaker <kragen@canonical.org> writes:
scott@slp53.sl.home (Scott Lurndal) writes:
Those clever people _were_ cranking out suitable systems languages by
the bucketful. (...), HP-3000 SPL (Systems Programming Language - I
used SPL in the late 70s)
With the caveat that I last used it a half century ago, I'd call it
a bit lower level (closer to the hardware) than C. It is tailored
around the stack-based HP-3000 architecture. As the HP3000 architecture
was influenced by ex-Burroughs large systems engineers, it is closer
to Burroughs ALGOL-based system languages than C.
ThatrCOs interestingrCerCorCethat wasnrCOt apparent from the parts of the manul I
glanced over. (I hope that doesnrCOt sound like I doubt you!) The HP
3000 didnrCOt 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 targetrCerCorCemore like the HP 9825 than like the >Burroughs 5500.
What did SPL do to expose the hardware that C doesnrCOt do? ThatrCOs
exactly the kind of insight I was hoping for when I saw your post! ItrCOs >difficult to extract such informtion from language manuals.
INTEGER ARRAY
Kragen Javier Sitaker <kragen@canonical.org> writes:
scott@slp53.sl.home (Scott Lurndal) writes:
Those clever people _were_ cranking out suitable systems languages by
the bucketful. (...), HP-3000 SPL (Systems Programming Language - I
used SPL in the late 70s)
With the caveat that I last used it a half century ago, I'd call it
a bit lower level (closer to the hardware) than C. It is tailored
around the stack-based HP-3000 architecture. As the HP3000 architecture
was influenced by ex-Burroughs large systems engineers, it is closer
to Burroughs ALGOL-based system languages than C.
The original HP-3000 was a stack-based architecture. Very similar to the Burroughs B6500 (the successor to the B5500). I believe that was emulated
on later models based on the PARISC processors. Arithmetic instructions
all popped the operands from the stack and pushed the result. No GPRs.
SPL/3000 directly exposed the stack to the programmer via the TOS keyword.
<I haven't typed in the rest of the hardcopy listing yet...>
Kragen Javier Sitaker <kragen@canonical.org> writes:...
...ThatrCOs interestingrCerCorCethat wasnrCOt apparent from the parts of the manul I
glanced over. (I hope that doesnrCOt sound like I doubt you!) The HP
3000 didnrCOt 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 targetrCerCorCemore 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).
On 2026-08-28 12:18, Scott Lurndal wrote:
There are a bunch of manuals here:
<https://bitsavers.org/pdf/hp/3000/>
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.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:35:59 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,563 |