Hamilton C shell
64-bit Hamilton C shell on a Windows 7 desktop. | |
Original author(s) | Nicole Hamilton |
---|---|
Initial release | December 12, 1988 |
Stable release | 5.2 / September 15, 2014 |
Written in | C |
Operating system | Windows |
Type | Unix Shell on Windows |
License | Commercial proprietary software |
Website |
www |
Hamilton C shell is a clone of the Unix C shell and utilities[1][2] for Microsoft Windows created by Nicole Hamilton[3] 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[4][5][6][7][8][9] and on Windows NT in July 1992.[10][11][12] 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, its compiler architecture, its use of threads, and the decision to follow Windows rather than Unix conventions.[8][9]
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 typed interactively but not very well on the more complex commands a user might take time to write in a script.[13] 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.
By contrast, Hamilton uses a top-down recursive descent parser that allows it to compile commands and procedures to an internal form before running them.[1][8] As a result, statements can be nested arbitrarily.[6]
Threads
Lacking fork or a high performance way to recreate that functionality, Hamilton uses the Windows threads facilities instead.[6][8] 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 follows Windows conventions instead of Unix conventions for filename slashes, escape characters, etc.[9]
References
- 1 2 Early Hamilton C shell Quick Reference (PDF). Hamilton Laboratories, Wayland, MA. Jul 10, 1990. Retrieved Nov 22, 2010.
- ↑ Faught, Danny (Aug 31, 1996). "The shell game". Software QA Magazine 3 (4). Retrieved Apr 8, 2013.
- ↑ The author has discussed her transition from Douglas Hamilton on a panel discussion at Stanford, beginning at 29:37. Nicole Hamilton, Carl Ingram, Liz Kennedy Myers, Tom Mills, John Ordway, Scott Thatcher, Kirstie Wilde (Moderator) (Nov 28, 2007). Class of 1972 Panel Discussion: Hell No We Won't Go (Quietly Into the Night)!. Stanford Alumni Association, iTunes U. Retrieved Nov 23, 2010.
- ↑ Machlis, Sharon. "Wayland writer for IBM" (PDF). Middlesex News (Dec 18 1988): 2E. Retrieved Nov 22, 2010.
- ↑ Sussman, Ann. "Hamilton C Shell Speeds Development Of OS/2 Applications" (PDF). PC Week (Dec 26 1988 - Jan 2 1989): 37. Retrieved Nov 22, 2010.
- 1 2 3 Hamilton, Douglas A. "Hamilton C shell Announcement" (PDF). IBM Personal Systems Developer (Summer 1989): 119–121. Retrieved Nov 22, 2010.
- ↑ Richman, Scott (Jan 1991). "Examining the Hamilton C Shell" (PDF). Dr. Dobb's Journal. Retrieved Nov 22, 2010.
- 1 2 3 4 Goutal, Kenneth G. "The Hamilton C shell" (PDF). MIPS Magazine (Sep 1989). Retrieved Nov 22, 2010.
- 1 2 3 Yager, Tom. "OS/2, Unix Style" (PDF). BYTE Magazine (Feb 1990). Retrieved Nov 22, 2010.
- ↑ Hamilton C shell for Windows Release Notes 4.0, retrieved June 19, 2010.
- ↑ 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. (Apr 1, 1998). "Hamilton C Shell". Windows IT PRo. Retrieved Mar 23, 2013.
- ↑ Csh Programming Considered Harmful by Tom Christiansen
- ↑ 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 Oct 8, 2010.