An Ethical History of Photography in Combat and of Combat Photography in the United States during World War II

With the United States‘ entry into the Second World War, the word ?censorship? was seen largely as antithetical to, rather than a necessary counterpart to, victory among Americans. People did not want to be censored in their writing, photographs or speech,but it proved to be necessary even before the war began, in order to protect government secrets and the people on the home-front from scenes that were too disturbing. Even before the war had officially begun, there were problems with censorship among journalists and newspapers. The initial response of outrage in reference to censorship in the United States was common among journalists, newspapers, magazines, and radio news; nevertheless, there was a necessity for censorship among Americans, on the home frontand the front lines, and it would be tolerated throughout the war to ensure that enemies of America did not gain access to information that would assist in a defeat of the United States in the Second World War. The research I have conducted has dealt with the censorship of combat photography during World War II, in conjunction with the ethics that were in play at the time that affected the censors. Through exploring the work of three combat photographers — Tony Vaccaro, James R. Stephens and Charles E. Sumners — I wasable to effectively construct an explanatory ethical history of these three men. Research on the censorship and effects it had on the United States brought me to three distinctareas of censorship and ethics that would be explored: (1) the restrictions and limitations enforced by the Office of Censorship, (2) a general overview of war and photography as it influenced the soldiers and their families on the home-front, (3) and the combat photographers and personal and military censorship that influenced their work. Although their work was censored both by the military and the government, these men saw the war in a different light that remained with them long after the battles and war had ceased.Using the narratives of Tony Vaccaro, Charles E. Sumners and James R. Stephens as means for more in depth research, this thesis strives to create lenses through which to view the history and ethics of censorship that shaped combat photography during the Second World War and the images to which we refer as representative of that war today.

Hoisting C Structures Into Clay In Device Drivers

This project addresses the unreliability of operating system code, in particular in device drivers. Device driver software is the interface between the operating system and the device's hardware. Device drivers are written in low level code, making them difficult to understand. Almost all device drivers are written in the programming language C which allows for direct manipulation of memory. Due to the complexity of manual movement of data, most mistakes in operating systems occur in device driver code. The programming language Clay can be used to check device driver code at compile-time. Clay does most of its error checking statically to minimize the overhead of run-time checks in order to stay competitive with C's performance time. The Clay compiler can detect a lot more types of errors than the C compiler like buffer overflows, kernel stack overflows, NULL pointer uses, freed memory uses, and aliasing errors. Clay code that successfully compiles is guaranteed to run without failing on errors that Clay can detect. Even though C is unsafe, currently most device drivers are written in it. Not only are device drivers the part of the operating system most likely to fail, they also are the largest part of the operating system. As rewriting every existing device driver in Clay by hand would be impractical, this thesis is part of a project to automate translation of existing drivers from C to Clay. Although C and Clay both allow low level manipulation of data and fill the same niche for developing low level code, they have different syntax, type systems, and paradigms. This paper explores how C can be translated into Clay. It identifies what part of C device drivers cannot be translated into Clay and what information drivers in Clay will require that C cannot provide. It also explains how these translations will occur by explaining how each C structure is represented in the compiler and how these structures are changed to represent a Clay structure.