A programming language defines one particular way to give instructions to a computer. It is comprised of rules about how those instructions should be formed and what they mean. As with human languages, there is a great diversity of programming languages, and as with human languages, they have evolved over time, developing out of predecessors and borrowing features from contemporaries. We can study programming languages in terms of those relationships (giving us rough groupings of language types, sometimes called "paradigms") and the various common features each language may or may not contain. Each language, designed with particular choices from the huge range of possibilities, thus has its own strengths, weaknesses, and varying suitability to various tasks to which we might apply it.
In this class, we will study these aspects of programming languages. We will focus on a few specific languages as examples of broader classes and as particular implementations of language features; the details will be broadly generalizable to large numbers of other languages. We will study and practice writing programs with a few new languages and learn about certain features in the context of languages you have studied previously (Python and C++).
By the end of the class, you will:
For an idea of the specific topics covered in the course, see the rough schedule for the semester.
Semester schedule — tentative - see Moodle for up-to-date details.
Moodle — assignments, quizzes, announcements, and other online resources will be here.
CS Codex resources for CS355 — collected resources and readings for this course.
There is no required textbook. We will use a variety of freely-available online resources and others I provide. If you prefer physical books, talk to me for recommendations.
The final grade will be based on the following breakdown:
| Assignments | 45% |
| Exam 0 | 5% |
| Exam 1 | 15% |
| Exam 2 | 15% |
| Final Exam | 20% |
Exams will be held in class, on paper. The final is cumulative. Exam 0 is a lower-stakes exam intended to familiarize you with the style of the exams before they become higher stakes.
Assignments will be posted on the course's Moodle site. You will use the Git version control system to store and manage your code for programming assignments. Effective use of Git will be one component of the rubric for grading such assignments. Each assignment will inclkude specific submission instructions.
Assignments will be due at set times; they will be considered late at any point after that time. An assignment will lose 10% of the total possible points for every day or partial day it is late, and after five days it will not be accepted.
Assignments can't be accepted at all after solutions have been handed out or the graded work has been returned to the class.
Every student has two "grace tokens" that they may use for extensions in instances where they are unable to complete work by the assigned deadline. To use a grace token on an assignment, send me an email before the assignment deadline, explain why you need an extension, and we will determine an appropriate extension, which will be granted with no grade penalty. Some assignments may not be eligible for grace tokens due to immediate use of or feedback on the submitted work, but most will be.
If you would like to request a regrade, submit a request to me in writing (via email) within one week of receiving the graded assignment, quiz, etc. Indicate exactly which part you believe deserves a different score and why.
If any concept, piece of code, compiler error, or anything else related to this course is ever unclear to you, please come see me during my office hours. One-on-one, I can help you bridge the gap from what you do understand to what you want to understand. It will generally be the easiest, fastest way to clarify something.
If you cannot attend any of my regularly scheduled office hours, I'm more than happy to setup another time to meet. Just let me know.
And to make sure that misunderstandings and difficulties do not go unaddressed, I will often ask that anyone who receives a C- or below on any assignment or exam come see me to see what we can do about improving that going forward.
I strongly encourage you to form study groups with your classmates, compare notes, explain concepts to one another, and generally help each other learn the material in this course.
Any material turned in for a grade must be your own individual work, though. You may work on concepts with other students, but I ask that you not discuss assigned problems until after the work has been turned in. Giving or showing your solutions or code to another student, or looking at theirs, is not allowed.
This has two goals: 1) ensure that grades are a reflection of each student's own work, and 2) avoid situations where one person solves a problem and another records the answer as their own work without really learning.
Copying code found online and submitting it as your own is plagiarism as well. You may include or adapt small snippets of code if you clearly and accurately cite the source of the code in a comment nearby (including a URL and a clear description of what was used/adapted). Code with a citation will not be reported as an academic honesty violation, but if the code you've used is a substantial portion of the problem you were supposed to solve, you may still lose points.
For details on the university's policies regarding academic honesty, please read the sections of the student handbook on conduct, cheating, and plagiarism. Cheating of any form can result in failing the course and a report to the associate provost. If you are ever unsure of whether something might be crossing that line, please err on the side of caution; you can also just ask me, and I'll be happy to provide guidance.
Illinois Wesleyan University strives to make all learning experiences as accessible as possible. If you anticipate or experience academic barriers based on a disability (including mental health and chronic or temporary medical conditions), it is your responsibility to register with Accessibility Services. Please note that accommodations are not retroactive and accommodations cannot be provided until I receive an email from Accessibility Services. Once the email is sent, please make arrangements with me as soon as possible to discuss your accommodations confidentially so they may be implemented in a timely fashion. For more information contact Accessibility Services by visiting 110 Holmes Hall, calling 309-556-3231, or emailing accessibility@iwu.edu.
Our university's mission statement includes, "The University through our policies, programs and practices is committed to diversity [...]" Our school and this course are made stronger by the mix of people that come into it bringing a diversity of ideas, experiences, and backgrounds. I expect everyone in this course — instructor, TA, and student — to contribute to an inclusive atmosphere that respects the diversity of all others in it. Dimensions of diversity can include sex, race, age, national origin, ethnicity, gender identity and expression, intellectual and physical ability, sexual orientation, income, faith and non-faith perspectives, socio-economic class, political ideology, education, primary language, family status, military experience, cognitive style, and communication style. The individual intersection of these experiences and characteristics must be valued in our community. If you have related concerns about the class environment or behavior of any in it (including me), please let me know, and I will do my best to address them. If you are not comfortable speaking with me about them, you may also bring concerns to the Associate Provost or the Office of Diversity and Inclusion.
Play around. Studying programming languages is like exploring a tool library. Different options are all around you, some familiar, some novel. There are many more than you have experience with, but each one was designed and created for some purpose. You can figure a few things out by looking at each one, or maybe reading a bit about it, but you won't really understand how they work unless you try them out and put them through their paces. So play around with them. Write small programs to see how they work. Run head-first into compiler and runtime errors, then reason about what those errors are telling you. See if you can use some new language feature to write more elegant or compact code than you would have before you knew about it. Make lots of little experiments. Try to have fun with it!