![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
|
It is my recollection that MAD stood for Michigan Algorithmic Decorder and not Michigan Algorighm Decoder. If anyone knows for certain, please make an entry on this talk page. JJ 00:56, 31 December 2005 (UTC)
Nope, "Michigan Algorithm Decoder" is correct. Jeff Ogden ( talk) 20:06, 1 July 2010 (UTC)
I distinctly remember it from my college days at University of Maryland. It was called Michigan Algorithmic Decoder. Maybe it had two names, depending on where it was used.— Preceding unsigned comment added by Rcleaver ( talk • contribs) 19:28, 21 July 2011 (UTC)
I did my masters thesis at MIT in 1964 and I am sure it was called "Algorithmic". Used for a lot of programming on Multicx system Richard Marks — Preceding unsigned comment added by 76.167.86.14 ( talk) 16:16, 7 April 2015 (UTC)
One other thing I distinctly remember, that is not mentioned anywhere in the article, is that you could use floating point subscripts and loop counters. — Preceding unsigned comment added by Rcleaver ( talk • contribs) 19:28, 21 July 2011 (UTC)
One of the first largish programs I wrote all by myself
(not counting some Fortran numerical routines
as part of a summer internship at Bell Labs)
was a RISK calculator. It produced a table
of the probability of winning (n armies fight m armies).
It was written in MAD.
Dennis
-- Jamplevia ( talk) 15:34, 17 April 2022 (UTC)
The statement, "played a minor role in the development of CTSS" is very dubious.
On CTSS, by 1965, most B-core loaded commands were written in MAD. -- Tom Van Vleck
B-core A.K.A. Core-B loaded commands (and libraries) refers to what is userland in Linux-speak.
![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
|
It is my recollection that MAD stood for Michigan Algorithmic Decorder and not Michigan Algorighm Decoder. If anyone knows for certain, please make an entry on this talk page. JJ 00:56, 31 December 2005 (UTC)
Nope, "Michigan Algorithm Decoder" is correct. Jeff Ogden ( talk) 20:06, 1 July 2010 (UTC)
I distinctly remember it from my college days at University of Maryland. It was called Michigan Algorithmic Decoder. Maybe it had two names, depending on where it was used.— Preceding unsigned comment added by Rcleaver ( talk • contribs) 19:28, 21 July 2011 (UTC)
I did my masters thesis at MIT in 1964 and I am sure it was called "Algorithmic". Used for a lot of programming on Multicx system Richard Marks — Preceding unsigned comment added by 76.167.86.14 ( talk) 16:16, 7 April 2015 (UTC)
One other thing I distinctly remember, that is not mentioned anywhere in the article, is that you could use floating point subscripts and loop counters. — Preceding unsigned comment added by Rcleaver ( talk • contribs) 19:28, 21 July 2011 (UTC)
One of the first largish programs I wrote all by myself
(not counting some Fortran numerical routines
as part of a summer internship at Bell Labs)
was a RISK calculator. It produced a table
of the probability of winning (n armies fight m armies).
It was written in MAD.
Dennis
-- Jamplevia ( talk) 15:34, 17 April 2022 (UTC)
The statement, "played a minor role in the development of CTSS" is very dubious.
On CTSS, by 1965, most B-core loaded commands were written in MAD. -- Tom Van Vleck
B-core A.K.A. Core-B loaded commands (and libraries) refers to what is userland in Linux-speak.