Annotation of papers/freem_history/freem_history.ms, revision 1.16
1.2 snw 1: \"
1.16 ! snw 2: \" $Id: freem_history.ms,v 1.15 2025/04/24 16:47:58 snw Exp $
1.2 snw 3: \" History of FreeM
4: \"
5: \" Copyright (C) 2025 Serena Willis
6: \"
1.3 snw 7: \" $Log: freem_history.ms,v $
1.16 ! snw 8: \" Revision 1.15 2025/04/24 16:47:58 snw
! 9: \" Reorganize document, add MUMPS language overview
! 10: \"
1.15 snw 11: \" Revision 1.14 2025/04/24 15:33:29 snw
12: \" Add table of ISC-acquired M implementations
13: \"
1.14 snw 14: \" Revision 1.13 2025/04/24 01:31:13 snw
15: \" Add biblio checker
16: \"
1.13 snw 17: \" Revision 1.12 2025/04/23 18:59:53 snw
18: \" Refine wording
19: \"
1.12 snw 20: \" Revision 1.11 2025/04/23 18:58:31 snw
21: \" Refine awkward paragraphing
22: \"
1.11 snw 23: \" Revision 1.10 2025/04/23 18:44:26 snw
24: \" Correct capitalization error in abstract
25: \"
1.10 snw 26: \" Revision 1.9 2025/04/23 18:40:00 snw
27: \" Improve footnotes
28: \"
1.9 snw 29: \" Revision 1.8 2025/04/23 15:12:13 snw
30: \" Improve wording
31: \"
1.8 snw 32: \" Revision 1.7 2025/04/23 15:05:45 snw
33: \" Fix typographical problems
34: \"
1.7 snw 35: \" Revision 1.6 2025/04/23 13:32:34 snw
36: \" Fix copyright symbol
37: \"
1.6 snw 38: \" Revision 1.5 2025/04/23 13:29:37 snw
39: \" Add copyright and license, shorten URLs
40: \"
1.5 snw 41: \" Revision 1.4 2025/04/22 18:16:06 snw
42: \" Remove references to FreeM as a database
43: \"
1.4 snw 44: \" Revision 1.3 2025/04/22 17:54:09 snw
45: \" Initial draft of FreeM History paper
46: \"
1.3 snw 47: \" Revision 1.2 2025/04/22 14:56:22 snw
48: \" Add comment header to FreeM History
1.2 snw 49: \"
1.3 snw 50: \"
51: .R1
52: database ../references.bib
53: move-punctuation
54: .R2
1.1 snw 55: .TL
56: The History of FreeM
57: .AU
58: Serena Willis
59: .AI
60: Coherent Logic Development
61: .AB
1.10 snw 62: Since 2014, the author has been the maintainer of the primary fork of the FreeM implementation of the M programming language and persistent global storage engine. In this paper, we will share some of the history of FreeM, as well as its current status and goals.
1.1 snw 63: .AE
64: .SH
1.15 snw 65: MUMPS Language Overview and History
1.1 snw 66: .PP
1.15 snw 67: \fIMUMPS\fR\(emnow generally referred to as \fIM\fR to distance it from the infectious disease\(emis an imperative, general-purpose, command-oriented programming language supporting persistent, hierarchical, sparse arrays. It includes high-level support for multi-user, multi-processing applications with flexible concurrency control.
1.1 snw 68: .PP
1.15 snw 69: MUMPS, being an acronym for \fIM\fRassachusetts General Hospital \fIU\fRtility \fIM\fRulti-\fIP\fRrogramming \fIS\fRystem, was developed by Neil Pappalardo, Robert A. Greenes, and Curt Marble of Dr. Octo Barnett's lab at Massachusetts General Hospital in 1966-1967.
1.3 snw 70: .[
1.15 snw 71: greenes1969
1.3 snw 72: .]
1.15 snw 73: Inspired by RAND Corporation's JOSS, and the TELCOMP and STRINGCOMP languages from Bolt, Beranek and Newman, MUMPS' earliest and most prominent use cases were in the field of health informatics.
1.3 snw 74: .[
1.15 snw 75: greenes1970
1.3 snw 76: .]
77: .[
1.15 snw 78: pendergrass1969
1.3 snw 79: .]
1.15 snw 80: .PP
81: MUMPS code is divided into program units referred to as \fIroutines\fR, which are roughly analagous to \fImodules\fR or \fIcompilation units\fR in more mainstream languages. Routines are then further divided into labels (or \fItags\fR in MUMPS parlance), which serve as entry points into the routine. Subroutines and functions (the latter known as \fIextrinsic functions\fR) are introduced as tags with an optional, parenthesized \fIformallist\fR, being a list of parameters expected by the subroutine or extrinsic function.
82: .PP
83: Perhaps the most unique feature of M, the \fIglobal\fR, is a persistent, hierarchical, sparse array allowing developers to easily implement database features directly in the application's primary development language:
84: .IP
85: .DS L
86: .ft C
87: ROUTINE ;
88: SET ^PEOPLE("Willis, Serena","DOB")="1980-12-01"
89: SET ^PEOPLE("Willis, Serena","SEX")="F"
90: SET ^PEOPLE("Willis, Serena","COUNTRY")="US"
91: .ft
92: .PP
93: The above routine would be called with \fIDO ^ROUTINE\fR, resulting in a data structure in fixed storage where the elements (known in M parlance as \fIsubscripts\fR), i.e., \fI"Willis, Serena"\fR, are automatically sorted on insertion, allowing for rapid retrieval. Rough analogues can be found in the \fIPICK\fR operating system, as well as BBN \fIFILECOMP\fR, the latter of which was a direct influence in the early development of M.
94: .KS
95: .PP
96: Early versions of M included \fIMGH MUMPS\fR from Massachusetts General Hospital, and \fIDigital Standard MUMPS\fR from Digital Equipment Corporation. Notably, early commercial versions of M were commercial software, somewhat limiting the language's spread outside of its ecological niche of health informatics.
1.16 ! snw 97: .TS
! 98: center tab(#);
! 99: Cb Cb
! 100: L L.
! 101: Vendor#Implementation
! 102: Mass. General Hospital#MGH MUMPS
! 103: Digital Equipment Corp.#Digital Standard MUMPS (DSM)
! 104: InterSystems Corp.#InterSystems Standard MUMPS (ISM), Open M, Cache, IRIS Data Platform
! 105: Data Tree#Data Tree MUMPS (DTM)
! 106: Micronetics#Micronetics Standard MUMPS (MSM)
! 107: Patterson & Gray#PSM-11, PSM-32, PSM-V
! 108: MGlobal International Inc.#CCSM, MacMUMPS, M Global MUMPS, M3 Lite
! 109: U.C. Davis#MicroMUMPS
! 110: Ray Newman#MUMPS V1
! 111: Fourth Watch Software LC#Reference Standard M (RSM)
! 112: Kevin O'Kane#Mumps-II, Open Mumps, GPL Mumps
! 113: M21 Ltd.#M21
! 114: Fidelity National Information Services#GT.M (Greystone Technology MUMPS)
! 115: YottaDB#YottaDB
! 116: Eugene Karataev#MiniM
! 117: .TE
! 118: .CD
! 119: .SM
! 120: \fIFigure 1. Partial list of M implementations.\fR
! 121: .NL
! 122: .LD
! 123:
1.15 snw 124: .KE
1.1 snw 125: .SH
1.15 snw 126: Early History of FreeM
1.1 snw 127: .PP
1.3 snw 128: FreeM was developed in Germany in the mid-1990s by a developer who went by the pseudonym \fIShalom ha-Ashkenaz\fR, whose actual identity remains unknown,
129: .[
1.9 snw 130: walters99
131: %P 19
1.3 snw 132: .]
1.14 snw 133: though it is thought by some that they are a dentist who learned C and developed FreeM on their own time. Shalom developed FreeM at a time when InterSystems Corporation (the company that developed the ISM implementation of M) was acquiring the majority of its competitors and absorbing their technology into their \fIOpen M\fR product, which would later become \fIInterSystems Cache\fR.
1.3 snw 134: .[
1.9 snw 135: ibid
136: %P 18
1.3 snw 137: .]
1.14 snw 138: .KS
139: .TS
140: center tab(#);
141: Cb Cb
142: L L.
143: Implementation#Year
144: DataTree MUMPS (DTM)#1993
145: Digital Standard MUMPS (DSM)#1995
146: .[
147: dsmAcquisition
148: .]
149: Micronetics Standard MUMPS (MSM)#1998
150: .TE
151: .CD
152: .SM
1.16 ! snw 153: \fIFigure 2. M implementations absorbed by InterSystems Corp.\fR
1.14 snw 154: .NL
155: .LD
156: .KE
1.15 snw 157: .PP
1.13 snw 158: Shalom wished to provide a community-driven, open-source implementation of M as a bulwark against the growing threat of single-vendor hegemony over the M language. Its design\(emas well as some of the documentation included with the original sources\(emindicate that FreeM was originally targeted to the MS-DOS family of operating systems. It made use of a very limited subset of the C library, and included instructions for renaming the MS-DOS style 8.3 filenames in order to compile under UNIX.
1.3 snw 159: .[
160: freemREADME
161: .]
1.5 snw 162: .KS
1.3 snw 163: .PP
164: At one point in FreeM's early history, Shalom ported FreeM from MS-DOS to SCO UNIX, the UNIX System V Release III-derived descendant of Microsoft XENIX, now known as SCO OpenServer\(ema platform still supported by FreeM today.
165: .[
166: portSCO
167: .]
168: This port brought support for the \fIscoansi\fR terminal type, including colors and ANSI X3.64 control mnemonics.
1.5 snw 169: .KE
1.1 snw 170: .SH
1.15 snw 171: Initial Involvement
172: .PP
173: The author's mentor in computer programming and UNIX was Lawrence Landis, who involved himself heavily in the M programming language ca. 1991. Mr. Landis promoted the M language to the author from 1991 forward, and first demonstrated FreeM to her in August 1998. In 2010, the author incorporated her company, Coherent Logic Development, learned M, and began doing contract work in M through Mr. Landis's company, Fourth Watch Software.
174: .PP
175: Mr. Landis was the owner of FreeM's SourceForge repository
176: .[
177: gumpSF
178: .]
179: , which had not been touched in a number of years, following Fidelity National Information Services' decision to release GT.M under a free software license. In August 2011, the author downloaded the source code for FreeM and did enough work on it to enable building and running under modern GNU/Linux systems and posted it to the \fImumpster.org\fR forums.
180: .[
181: freem014
182: .]
183: .PP
184: In 2014, Mr. Landis gave the author administrator access to the FreeM SourceForge repository and transferred maintainership of the project to her.
185: .[
186: gumpSF
187: .]
188: .SH
1.11 snw 189: Generic Universal M Project
1.1 snw 190: .PP
1.5 snw 191: The \fIGeneric Universal M Project\fR was conceived by Richard F. Walters, a professor from U.C. Davis. The GUMP, following the rising popularity of object-oriented programming in the 1990s, was intended to be a toolkit allowing M implementations to be built from discrete components with a well-defined and well-specified public interface among these components. These components included the global handler (supplying the functionality of persistent global storage), and the interpreter/compiler (responsible for implementing M language commands). The components would have been able to communicate over a network, or in-process on the same host, enabling distributed computing functionality.
1.3 snw 192: .[
193: c2m
194: .]
195: .PP
196: Although the specification for the GUM interface to global handlers attained a reasonably well-specified level of completeness,
197: .[
198: gumapi
199: .]
1.9 snw 200: and Lawrence Landis and others developed a mostly-complete implementation of a GUM global handler,
1.3 snw 201: .[
202: gumpsrc
203: .]
204: none of the other envisioned components were ever completed, and specifically, the interpreter component was missing.
1.1 snw 205: .SH
206: Shalom's Gift
207: .PP
1.5 snw 208: In July of 1998, Shalom ha-Ashkenaz donated the FreeM source code (then known as FreeMUMPS) to the M User's Group-Deutschland (MUG-D), hoping the community would take the nascent implementation from its infancy through to a state of production-ready completeness and robustness. Shalom also placed a few conditions on his gift: a public release could not be made until a substantial set of milestones were reached. Per his conditions, the FreeMUMPS project must:
1.3 snw 209: .[
210: freemREADME
211: .]
1.1 snw 212: .IP \(bu 2
213: Implement the entirety of \fIANSI X11.1-1995\fR
214: .IP \(bu 2
215: Use Structured System Variables instead of \fIVIEW\fR commands and \fI$VIEW\fR functions
216: .IP \(bu 2
217: Raise the string size limits
218: .IP \(bu 2
219: Implement MWAPI, OMI, X11 bindings, and GKS bindings
220: .IP \(bu 2
221: Be substantially free of major bugs
222: .PP
223: Although MUG-D readily accepted the contribution of FreeMUMPS, the organization itself lacked the manpower and expertise to complete the implementation. Just as it is now, the intersection of M community members who know enough of the M language and C language to work on a project this ambitious was quite small.
1.11 snw 224: .SH
1.7 snw 225: .KS
1.1 snw 226: Merging GUMP and FreeM
227: .PP
1.5 snw 228: Very shortly after the contribution of FreeMUMPS to MUG-D, Richard F. Walters and a small team of developers and administrative staff who had been working on the GUMP assumed maintainership of the FreeMUMPS source code, with Lawrence Landis managing the development efforts.
1.3 snw 229: .[
1.9 snw 230: shortWalters99
231: %P 19
1.3 snw 232: .]
233: This included representatives from the \fIM Technology Association\fR (an M vendor association having several foreign branches), the \fIM Development Committee\fR (the M standards organization hosting the ANSI/ISO standards for the M language, then sponsored by the M Technology Association), and others.
234: .[
235: freemContributors
236: .]
237: The goals of this team were to:
1.1 snw 238: .IP \(bu 2
239: Meet Shalom's requirements for a public release of FreeMUMPS
240: .IP \(bu 2
241: Convert FreeMUMPS into the first interpreter component of the GUMP
1.11 snw 242: .KE
1.1 snw 243: .PP
1.5 snw 244: During this period, Ronald L. Fox of Diagnostic Laboratory Services in Honolulu, HI (who passed in 2010)
1.3 snw 245: .[
246: ronFoxGrave
247: .]
248: ported FreeMUMPS from SCO UNIX to Red Hat 5 and glibc-6.
249: .[
250: ronFoxPort
251: .]
252: Steve "Saintly" Zeck of the U.C. Davis Veterinary Medical Teaching Hospital
253: .[
254: saintlyBio
255: .]
256: also attempted to rewrite the symbol table code to lift string size limits,
257: .[
258: saintlySymtab
259: .]
1.8 snw 260: David Whitten enhanced some of the implementation-specific extensions, and Lawrence Landis integrated Zeck's symbol table work.
1.3 snw 261: .PP
1.5 snw 262: In FreeM 0.1.0, the name of the implementation was changed from FreeMUMPS to Public Standard M, and again to Free Standard MUMPS and then FreeM when it was discovered leading up to the FreeM 0.2.0 release that the PSM acronym was already in use for Patterson & Gray's
1.3 snw 263: .[
264: mdc_implementations
265: .]
266: M implementation.
267: .[
268: Changes.GUM
269: .]
270: Dr. Walters also received the implementation ID of 49 from then secretary of the M Development Committee, Don Piccone.
271: .[
1.9 snw 272: ibid
1.3 snw 273: .]
1.1 snw 274: .PP
1.5 snw 275: One of the contributors to FreeM at this stage\(emprimarily in the area of M vendor routines\(emwas Axel Trocha, who would later maintain a private fork of FreeM.
1.3 snw 276: .[
277: trochaFork
278: .]
1.7 snw 279: .KS
1.1 snw 280: .SH
281: The GT.M Free Software Release
282: .PP
283: GT.M, an acronym for \fIGreystone Technology MUMPS\fR, is an M implementation that was released by Greystone Technology in 1986. Greystone was later acquired by Sanchez Computer Associates, which was in turn acquired by Fidelity National Information Services.
1.3 snw 284: .[
285: fisSanchezAcquisition
286: .]
287: .PP
288: When GT.M was released under the GNU General Public License in 2000,
289: .[
290: gtmRelease
291: .]
1.5 snw 292: it seemed to many to negate the entire \fIraison d'etre\fR for FreeM, as GT.M was a well-established, robust, and high-performance M implementation with which FreeM could not then compete. Unfortunately, at this time, the GUMP and FreeM projects lost all of their momentum, and new development along these lines rapidly ceased. The final GUMP team release of FreeM was 0.5.0.
1.3 snw 293: .[
294: freem050
295: .]
296: However, Axel Trocha's private port would continue to be developed for some years.
1.7 snw 297: .KE
1.1 snw 298: .SH
299: Axel Trocha's Fork
300: .PP
1.11 snw 301: When the free software release of GT.M stalled the GUMP team's progress on the primary branch of development, Axel Trocha, an aforementioned contributor, continued development on the FreeM source code. Trocha added many interesting features to the FreeM codebase, including:
1.1 snw 302: .IP \(bu 2
303: A native port to Microsoft Windows
304: .IP \(bu 2
305: Compiling FreeM as an Apache web server module, allowing FreeM to be used easily for web development
306: .IP \(bu 2
307: The ability to output HTML code in a heredoc-style format, with any line of code beginning with a left angle bracket being interpreted as HTML with support for interpolated M locals and globals
308: .IP \(bu 2
309: Extensions allowing FreeM to be used as a command-line shell, along the lines of UNIX \fIbash\fR, Windows \fIcmd.exe\fR, etc.
310: .PP
1.5 snw 311: Trocha also maintains ownership of the \fIfreem.net\fR Internet domain,
1.3 snw 312: .[
313: trochaDomain
314: .]
1.15 snw 315: and continued issuing public releases of his FreeM port on that site until sometime after 2004, at which point this fork was made entirely private. Currently, freem.net is a blank page. However, trocha's fork of FreeM continues to the present as the back-end storage engine and programming environment for the \fIElven Runes\fR website.
1.3 snw 316: .[
317: elvenRunes
318: .]
1.5 snw 319: The author has communicated with Mr. Trocha on occasion, and though he is supportive of the author's efforts, has chosen to remain in the background.
1.1 snw 320: .SH
321: Resuming Primary Development Branch
322: .PP
323: In 2011, the author downloaded the FreeM source code from the GUM Project's SourceForge repository\(emdormant since 2000\(emand updated it just enough that it would compile and run on modern GNU/Linux systems. The author also quickly updated FreeM to support terminal sizes larger than 80x24.
324: .SH
325: Taking Maintainership
326: .PP
1.5 snw 327: In 2014, Lawrence Landis transferred administrative access of the GUMP repository, conferring maintainership of the primary branch of FreeM development to the author. Since then, many features have been added and many bugs corrected, including:
1.3 snw 328: .IP \(bu 2
329: Adding support for proper namespaces, configured through a \fIfreem.conf\fR file, which standardizes routine and global storage locations
330: .IP \(bu 2
331: Adding support for Structured System Variables
332: .IP \(bu 2
333: Adding support for the asynchronous event specification from MDC Type A proposal \fIX11/1998-28\fR
334: .[
335: x119828
336: .]
337: .IP \(bu 2
338: Adding support for constants via the \fICONST\fR keyword
339: .IP \(bu 2
340: Adding a \fIWITH\fR command allowing the specification of an implicit prefix to all subsequent variable references
341: .IP \(bu 2
342: Adding a runtime \fIWATCH\fR command, tracking changes to specified local or global variables
343: .IP \(bu 2
344: Adding an \fIASSERT\fR command, which will fail with an error message if the following expression evaluates \fIfalse\fR
345: .IP \(bu 2
346: Removing the Steve Zeck symbol table implementation\(emwhich was unreliable\(emand reverting to the original implementation
347: .IP \(bu 2
348: Adding support for the GNU \fIreadline\fR library, with persistent command line history and editing
349: .IP \(bu 2
350: Adding REPL-like functionality (in direct mode, any M expression beginning with a number will be prepended with an implicit \fIWRITE\fR)
351: .IP \(bu 2
352: Adding transaction processing
353: .IP \(bu 2
354: Adding \fIKVALUE\fR and \fIKSUBSCRIPTS\fR
355: .IP \(bu 2
356: Preparing to support the \fIM Windowing API\fR (MWAPI)
357: .IP \(bu 2
358: Adding the \fIfmadm\fR command-line utility, for system administration functions
359: .IP \(bu 2
360: Adding support for after-image journaling and forward recovery of globals
1.5 snw 361: .KS
1.3 snw 362: .IP \(bu 2
363: Writing a \fItexinfo\fR manual, from which the HTML manual is derived
364: .IP \(bu 2
365: Porting to Solaris/SPARC, Solaris/x86, Linux/s390x, Linux/armv6l, Linux/armv7l, SCO OpenServer 5.0.7, Tru64 UNIX/alpha, AIX/ppc, Mac OS X/x86, GNU HURD, Cygwin, NetBSD, FreeBSD, OpenBSD, and WSL1/2
1.11 snw 366:
1.5 snw 367: In addition, the FreeM web site
1.3 snw 368: .[
369: freemWebsite
370: .]
371: was created, to distribute downloads and documentation.
1.5 snw 372: .KE
1.3 snw 373: .SH
374: Future
375: .PP
1.5 snw 376: FreeM is envisioned as a client-oriented desktop M implementation, for developing graphical user interfaces that will run on mobile and desktop devices.
1.3 snw 377: .PP
378: The author also intends to adopt the original vision of the GUMP team, dividing FreeM's functionality into discrete components having a well-specified public interface, with the ability to run in distributed computing environments over a network.
379: .PP
380: FreeM's mission is to advance the state-of-the-art in M implementations, and push the evolution of the language forward. Maintaining portability to as many vintage and modern UNIX systems as possible is held as a high priority, while portability of M routines and MDC standards compliance will be maintained through the use of the new \fI$ZDIALECT\fR intrinsic special variable to ensure that such compliance does not conflict with the primary goal of elegantly advancing the state-of-the-art and finding new audiences for the concepts originated by Neil Pappalardo and Octo Barnett in 1966.
381: .PP
382: The FreeM project is also strongly committed to free software principles, and is firmly aligned with the goals of the GNU Project and the Free Software Foundation, believing that the ethical concerns surrounding proprietary software are at least as important as the practical concerns espoused by the Open Source movement.
383: .[
384: whyFreeSoftware
385: .]
1.5 snw 386: .SH
387: Conclusion
388: .PP
1.7 snw 389: FreeM has seen a colorful and turbulent history, touched by many capable hands. Though public development of any strain of the implementation was dormant for nearly a decade, fourteen years of almost continuous development have passed since the project resumed in 2011, and a decade since official maintainership passed in 2014, and great progress has been made.
390: .PP
391: FreeM\(emas is the case for all M projects\(empresses forward in a period where the future of the M programming language is uncertain. M Development Committee efforts concurrent with FreeM development have been sporadic and have missed many milestones, the community's most prominent members are aging, and many organizations have migrated from large M applications to what is perceived as more "modern" replacements.
392: .PP
393: It is the opinion of the author that the tight integration of an expressive and dynamic language with a robust and performant persistent storage engine makes M a natural candidate for many new and general applications. Modern application development is plagued by overwhelming bars to entry, requiring mastery of many languages and database management systems and the bulky interfaces connecting them.
394: .PP
1.11 snw 395: Though not without significant warts accreted over the years, M has no such overhead. Thus, FreeM seeks to press its philosophical advantages by mitigating the language's accumulated cruft, and adding clean interfaces addressing the needs of today. With these goals in mind, development proceeds apace.
1.7 snw 396: .KS
1.5 snw 397: .SH
398: Copyright and License
399: .LP
1.6 snw 400: This document is Copyright \[co] 2025 Serena Willis
1.5 snw 401: .LP
402: Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License,
403: .[
404: gfdl
405: .]
406: Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover texts, and with no Back-Cover Texts.
407: .LP
1.16 ! snw 408: \fI$Id: freem_history.ms,v 1.15 2025/04/24 16:47:58 snw Exp $\fR
1.7 snw 409: .KE
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to freem_history.ms CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Coherent Logic Development] / papers / freem_history