<p>Writing concurrent programs using shared memory causes many programmers much trouble, due primarily to unsafe semantics. Memory corruption, race conditions, deadlocks, and even livelocks are trivially easy to introduce into a program and painful to hunt down due the nearly infinite possible interleavings of instructions between the threads.</p> <p>Undergraduate curricula traditionally introduce students to the idea of shared memory multithreading in a systems programming or operating systems class, but rarely expose them to any alternate models of concurrent programming. This leaves them with the idea that shared memory is the only way to do concurrent programming. </p> <p>After students were exposed to alternate models, they came to prefer them to the standard shared memory model. This happened despite their distaste of the programming language that was utilized in performing the study. The students also expressed interest in alternate models of concurrency being taught in the computer science curricula at WPI.</p>

Creator

• Lieb, Christopher

Contributors

• Pollice, Gary F.

Degree

• MS

Unit

• Computer Science

Publisher

• Worcester Polytechnic Institute

Language

• English

Identifier

• etd-042611-112809

Keyword

• csp
• concurrency
• actors
• Education
• channels
• study

Advisor

• Pollice, Gary F.

Defense date

• 2011-04-26

Year

• 2011

Date created

• 2011-04-26

Resource type

• Thesis

Rights statement

• In Copyright

Last modified

• 2021-02-02