On 5/10/24 16:37, Fred Cisin via cctalk wrote:
> I was told that some of the many locally applied patches were done by
> writes to array elements with negative subscripts.
>
CDC 6000 (the one with PPUs) OS (SCOPE, KRNONOS, MACE and NOS) used a
single PPU that, among other things, monitored the c
On Fri, 10 May 2024, Charles via cctalk wrote:
Regarding protections, it didn't have many. I remember spending a day
tracking down a fatal bug with a logic analyzer (emulators were still a dream
in this small company)... another programmer had used an array subscript out
of range and the compil
In the early '80's, I did some programming with Micro Concurrent Pascal,
on embedded CDP1802 systems. It was really nice to be able to program in
something other than assembly language (a cross-assembler that ran on a
PDP-11 system).
Regarding protections, it didn't have many. I remember spend
Microsoft had to pay $120 million, and Stac had to pay $13.6 million.
But Microsoft also settled some claims out of court with a $39.9 million
dollar investment in Stac, and paid $43 million in royalties.
Yes, billg had a bad day. comparable to my losing $100
On Fri, 10 May 2024, Sellam Abraham
On Fri, May 10, 2024, 3:38 PM Fred Cisin via cctalk
wrote:
>
> Microsoft had to pay $120 million, and Stac had to pay $13.6 million.
> But Microsoft also settled some claims out of court with a $39.9 million
> dollar investment in Stac, and paid $43 million in royalties.
> Yes, billg had a bad da
On 2024-05-10 1:01 p.m., Chuck Guzis via cctalk wrote:
There have been some minor skirmishes in the MCU world over what
language should be used when programming.
EASY! OCTAL! If it worked on the 8 it is good enough for me.
C/C++ is very much top dog, probably because the development suites a
Please note, that I am NOT saying that there was nothing wrong in the
compression. Merely that the disasters that prompted the public outcry
were due to SMARTDRV's problems, not the problems with the compression.
My numbers were all wrong on the Microsoft V Stac lawsuit.
Micorsoft and Stac ha
On 5/10/24 14:44, Doug Jackson via cctalk wrote:
> C didn't enter my world until I started running FreeBSD in the late 90's
> where it was essentially part of the OS. I remember paying $600 bucks AUD
> for a Borland C compiler running under Windows, but the whole concept of
> writing a simple app
Circa 1986 I was working at the Research School of Physical Sciences at the
Australian National University.
As late as that we were still running CP/M on an eclictic mix of Imsai8080
and STD Bus based machines. These were all running laboratory
experiments.
Turbo Pascal was king in that environm
very slow and buggy. I heard a story that to speed up disc access, MS put
FAT-manipulation code in the actual compiler and that occasionally
destroyed the FAT.
Sorry Stuff, ain't so.
If you had FAT corruption issues, perhaps you had SMARTDRV enabled with
write cacheing (which did occasionally m
On 5/10/24 14:03, Sellam Abraham via cctalk wrote:
> On Fri, May 10, 2024 at 1:36 PM Fred Cisin via cctalk
> wrote:
> I developed quite a bit and for many years with Microsoft C v6.0 under DOS
> and it was not bad. The compiler was decently fast and once 486s and then
> Pentiums became available
> From: Fred Cisin via cctalk [mailto:cctalk@classiccmp.org]
> Sent: Friday, May 10, 2024 4:36 PM
> To: Stuff Received via cctalk
> Cc: Fred Cisin
> Subject: [cctalk] Re: DOS p-System Pascal: (Was: Saga of CP/M)
>
> Sorry Stuff, ain't so.
>
> Bob Wallace wrote the Microsoft Pascal compiler, whi
While doing my customary "whatever happened to" sweep, I ran across this
paper of Jules Schwartz (he of JOVIAL) A refreshingly frank evaluation
from the author from 1978.
http://jovial.com/documents/p203-schwartz-jovial.pdf
(Tidbit: The "J" in JOVIAL does stand for "Jules'", but was not of his
On Fri, May 10, 2024 at 1:36 PM Fred Cisin via cctalk
wrote:
> On Fri, 10 May 2024, Stuff Received via cctalk wrote:
> > I recall that MS sold a Pascal compiler, possibly from someone else. It
> was
> > very slow and buggy. I heard a story that to speed up disc access, MS
> put
> > FAT-manipula
On Fri, 10 May 2024, Stuff Received via cctalk wrote:
I recall that MS sold a Pascal compiler, possibly from someone else. It was
very slow and buggy. I heard a story that to speed up disc access, MS put
FAT-manipulation code in the actual compiler and that occasionally destroyed
the FAT.
S
On Fri, 10 May 2024 12:00:07 -0500
cctalk-requ...@classiccmp.org wrote:
> The UCSD shell was atrocious. The compiler was slow. The editor was
> terrible. The entire experience was reminiscent of working on a dumb
> terminal connected to a mainframe, when it could've taken advantage of
> the fea
There have been some minor skirmishes in the MCU world over what
language should be used when programming.
C/C++ is very much top dog, probably because the development suites are
written for that.
There's a small group that advocates Python; and some say that Ada is
best. But they represent a ve
On 2024-05-09 09:46, Warner Losh via cctalk wrote:
On Thu, May 9, 2024, 5:39 AM Bill Degnan via cctalk
wrote:
Without doing the research before asking, there was the UCSD p-System
Pascal for IBM PC which came out very early in the history of the IBM PC.
It was not very popular. The SAGE II th
After 'lunch with Draper', you almost immediately reference a 'CRUNCH'
utility? Seems like more than coincidence to me, but I'm big on
conspiracy theories.
On Fri, May 10, 2024 at 8:45 AM Paul Koning via cctalk
wrote:
> I suppose you could pose ESPOL as an example of a language for a machine,
ESPOL was likely a major inspiration for SPL (System Programming
Language) for the Classic stack-based HP 3000 which was used to write
the MPE operating syste
> On May 10, 2024, at 11:16 AM, Sellam Abraham via cctalk
> wrote:
>
> On Fri, May 10, 2024, 7:53 AM Chuck Guzis via cctalk
> wrote:
>
>> There's a third class that I haven't (yet) mentioned. Design a machine
>> to solve a particular problem or class of problems. Saxpy was such a
>> machi
On Fri, May 10, 2024, 7:53 AM Chuck Guzis via cctalk
wrote:
> There's a third class that I haven't (yet) mentioned. Design a machine
> to solve a particular problem or class of problems. Saxpy was such a
> machine; we have bitcoin ASICs and our latest AI ventures.
>
> What was the CM-1 programm
On Sat, 4 May 2024 at 17:28, Gianluca Bonetti via cctalk
wrote:
>
> I am helping Museo del Computer with this fundraising effort in order to
> save a large number of machines with significant historic value, including
> some Sperry Univac systems.
I shared the links on Vintage Computer Club on Fa
On 5/10/24 06:44, Paul Koning wrote:
>
> As for "language to the machine" that's pretty much unheard of. While there
> certainly are languages that only were seen on one or a few machines or
> architectures -- SYMPL, CYBIL, BLISS, TUTOR -- it isn't because that was the
> intent of those languag
> On May 9, 2024, at 8:58 PM, Chuck Guzis via cctalk
> wrote:
>
> On 5/9/24 16:30, Michael Thompson wrote:
>> I have a source code tape for Pascal on a CDC 6600 from CDC in France.
>> I am not sure which version it is.
>
> Broadly speaking, there were only three major CDC versions; the 1972
First one. Sounds vintage, is not musically annoying like most of the others,
and has a nice easter egg in it.
Marc
> On May 9, 2024, at 12:31 PM, John Herron via cctalk
> wrote:
>
> Do you know who your demographic or age is that you're trying to attract to
> watch the videos?
>
>> On Fri,
26 matches
Mail list logo
