These are some of the topics we've discussed or read about. The list is not necessarily complete.
I have not yet decided on the format for the exam. When last I taught I course like this, I gave a take-home exam with questions similar to those on the homeworks. This will be a fifty minute exam, so it is likely to have a different format. As you may have noted, I generally ask questions that ask you to synthesize knowledge from different topics we've covered. I am likely to ask you to criticize a language design, develop a grammar, compare types, and analyze variables.
How should you study for the exam? Well, it depends on who you are and how you learn best. I'd suggest some of the following:
These policies (or a very similar set) will appear at the front of the exam.
This examination is open book, open notes, open mind, open computer, open web. Feel free to use any and all resources available to you except for other people. As always, you are expected to turn in your own work. If you find ideas in a book or on the web, be sure to cite them.
I strongly recommend that you read over the whole exam before attempting to answer any questions.
Answer all of your questions in a blue book. If you would prefer to, you may write all of your answers on the computer and print them out at the end of class. If you write your answers in the blue book, you need not do the problems in order (but it would help me if you provided a table of contents). If you type your answers on the computer, please do them in order.
I will give partial credit for partially correct answers. You ensure the best possible grade for yourself by highlighting your answer and including a clear set of work that you used to derive the answer.
I will not be available during the exam. If you feel that a question is badly worded or impossible to answer, note the problem and attempt to reword the problem in such a way that it is answerable.
In some questions, you may be asked to write code. You should feel free to write pseudocode in any reasonable form (i.e., similar to any common language). Your pseudocode need not be "syntactically correct". However, it should be clear and should indicate to me that you would be able to write correct and working code (in some language) if you had sufficient time.
Disclaimer Often, these pages were created "on the fly" with little, if any, proofreading. Any or all of the information on the pages may be incorrect. Please contact me if you notice errors.
Source text last modified Fri Feb 20 09:57:54 1998.
This page generated on Fri Feb 20 10:01:07 1998 by SiteWeaver.
Contact our webmaster at email@example.com