Hamilton C shell
 64-bit Hamilton C shell on a Windows 7 desktop. | |
| Original author(s) | Douglas Hamilton |
|---|---|
| Initial release | December 12, 1988 |
| Stable release | 5.2.g
/ March 5, 2017 |
| Written in | C |
| Operating system | Windows (historically OS/2) |
| Type | Unix Shell on Windows |
| License | Commercial proprietary software |
| Website | hamiltonlabs |
Hamilton C shell is a clone of the Unix C shell and utilities[1][2] for Microsoft Windows created by Douglas Hamilton at Hamilton Laboratories as a completely original work, not based on any prior code. It was first released on OS/2 on December 12, 1988[3][4][5][6][7][8] and on Windows NT in July 1992.[9][10][11] The OS/2 version was discontinued in 2003 but the Windows version continues to be actively supported.
Design
Hamilton C shell differs from the Unix C shell in several respects. These include its compiler architecture, its use of threads, and the decision to follow Windows rather than Unix conventions.[7][8]
Parser
The original C shell uses an ad hoc parser. This has led to complaints about its limitations. It works well enough for the kinds of things users type interactively but not very well for the more complex commands a user might take time to write in a script. It is not possible, for example, to pipe the output of a foreach statement into grep. There was a limit to how complex a command it could handle.[12]
By contrast, Hamilton uses a top-down recursive descent parser that allows it to compile statements to an internal form before running them.[1][7] As a result, statements can be nested or piped arbitrarily.[5] The language has also been extended with built-in and user-defined procedures, local variables, floating point and additional expression, editing and wildcarding operators, including an "indefinite directory" wildcard construct written as "..." that matches zero or more directory levels as required to make the rest of the pattern match.[13]
Threads
Lacking fork or a high performance way to recreate that functionality, Hamilton uses the Windows threads facilities instead.[5][7] When a new thread is created, it runs within the same process space and it shares all of the process state. If one thread changes the current directory or the contents of memory, it's changed for all the threads. It's much cheaper to create a thread than a process but there's no isolation between them. To recreate the missing isolation of separate processes, the threads cooperate to share resources using locks.[14]
Windows conventions
Hamilton differs from other Unix shells in that it also directly supports Windows conventions for drive letters, filename slashes, escape characters, etc.[8]
References
- ^ a b Early Hamilton C shell Quick Reference (PDF). Hamilton Laboratories, Wayland, MA. Jul 10, 1990. Retrieved July 28, 2016.
- ^ Faught, Danny (Aug 31, 1996). "The shell game". Software QA Magazine. 3 (4). Archived from the original on March 1, 2012. Retrieved Apr 8, 2013.
- ^ Machlis, Sharon. "Wayland writer for IBM" (PDF). Middlesex News (Dec 18 1988): 2E. Retrieved July 28, 2016.
- ^ Sussman, Ann. "Hamilton C Shell Speeds Development Of OS/2 Applications" (PDF). PC Week (Dec 26 1988 – Jan 2 1989): 37. Retrieved July 28, 2016.
- ^ a b c Hamilton, Douglas A. "Hamilton C shell Announcement" (PDF). IBM Personal Systems Developer (Summer 1989): 119–121. Retrieved July 28, 2016.
- ^ Richman, Scott (Jan 1991). "Examining the Hamilton C Shell" (PDF). Dr. Dobb's Journal. Retrieved July 28, 2016.
- ^ a b c d Goutal, Kenneth G. "The Hamilton C shell" (PDF). MIPS Magazine (Sep 1989). Retrieved July 28, 2016.
- ^ a b c Yager, Tom. "OS/2, Unix Style" (PDF). BYTE Magazine (Feb 1990). Retrieved July 28, 2016.
- ^ Hamilton C shell for Windows Release Notes 4.0, retrieved July 28, 2016.
- ^ Hamilton, Doug (Jul 27, 1995). "Looking for C-Shell on NT". Newsgroup: comp.os.ms-windows.nt.misc. Usenet: hamilton.806823765@BIX.com. Retrieved Oct 8, 2010.
- ^ Deignan, Michael P. (March 31, 1998). "Hamilton C Shell". Windows IT Pro. Retrieved September 22, 2019.
- ^ Csh Programming Considered Harmful by Tom Christiansen
- ^ "Wildcarding and pattern matching". Hamilton Laboratories. Retrieved August 13, 2018.
- ^ Hamilton, Doug (Apr 21, 1995). "Suggestions for multiple-reader/single-writer lock?". Newsgroup: comp.os.ms-windows.nt.misc. Usenet: hamilton.798430053@BIX.com. Retrieved July 28, 2016.