3.6 Language Analysis the First
Most students want a suggestion about how much they should write. It doesn’t matter how much you write, provided you give a thoughtful analysis. It is possible to write a great 4 page paper and a terrible 14 page paper. Focus on writing a good paper.
I find that most good papers are about 7 pages.
Since you are turning in text files, it may be difficult to evaluate the page length. When I run a2ps -1 on a text file, it prints about 66 lines per page. So, 7 pages is about 455 lines.
If you are having trouble sticking to 80-character lines in a text file, it is easy to use auto-fill-mode in Emacs or just press Meta-q periodically while you are typing in Emacs.
Write a survey paper about an existing programming language, of your choice.
You should analyze it using the critical tools, terminology and ideas used in this class. You should discuss what makes it unique or interesting. You could talk about what you believe is particularly good or bad about it. You could talk about how to improve it.
I find that students have a hard time getting beyond description and going into discussion and analysis. Try very hard. Come ask me for advice if you don’t understand or are worried.
You should limit your discussion of the history of the language, but it may be interesting to spend a little time on it (not more than a page, probably.)
You should be judicious in your discussion of implementations of the language or implementation techniques. But, in some cases, there may be something particularly important about an implementational matter that would be worth discussing.
You should /severely/ limit your use of code samples. It is much better to explain the language with words.
You must properly cite the sources for your information.
You should not pad your writing or include bologna.
I strongly advise you to choose a language that you are not already familiar with, so that you will learn more. In addition, it is probable that the more "mainstream" a language is, the less unique or interesting it is, so it will be more difficult to actually write the paper.
When I am grading, I will assume you have a perfect paper and then I will take off 5% for every flaw. You should follow this same algorithm when grading yourself or others. (Examples of flaws: typos, missing citations, poor grammar, poor arguments, pandering, padding, bad style, etc.) However, I won’t take off more than 25% for grammar and typos (but I will ignore the sentences/etc where they appear after that, so your argument may break.)
This rubric is deliberately vague to encourage you to talk to me about your writing assignments. In addition, I will review your assignment as many times as you want to help you know how to improve it.