This course meets from 9:00 to 9:50 AM Mondays, Wednesdays, and Fridays, in HHE 110 (formerly known as Business 110).
Note: Please look through the examples directory; I've put a lot of examples there, many of them improved or "cleaned up" from the versions I showed you in class. For example, I showed 15 versions of the GUI program on November 7, but there are 21 versions on the Web. And on November 10, I demonstrated console and file I/O; there are cleaner versions of those on the Web, and there's an example of network I/O (reading from a Web page).
I recommend Eclipse, which is available for free download and works with several different languages.
Another possibility is jGRASP, which has fewer bells and whistles, but provides a cute graphical annotation of the control flow of your program.
Yet another is BlueJ, a Java environment designed for teaching introductory programming.
For learning Prolog on Windows I recommend the Amzi Prolog + Logic Server. The latest release (7.0.7) of Amzi Prolog is actually an Eclipse plug-in; you can download it for free for Windows or Linux. If you've already got Eclipse, you can download only the 6MB Amzi! Core ; if not, you'll need the 40MB package which includes the Eclipse IDE as well. In either case, you'll need to have already installed Java.
I've installed the documentation for Amzi's Eclipse IDE and the language tutorial Adventure in Prolog on Adelphi's Web server; if you install Amzi Prolog on your own machine, you'll have your own local copies of these.
This course is intended primarily for students majoring or minoring in computer science or information systems. It assumes CSC 171 and 172 as prerequisites. If you're taking 172 concurrently with 270, you'll have a more difficult time, but you should be able to survive the course; talk to the instructor.
The official subject of this course is programming languages. But I feel it would be irresponsible to teach programming languages without discussing software engineering at the same time. Software engineering includes such simple ideas as the "edit-compile-run-debug" cycle you all learned in last year's CS courses, the aspects of "programming style" I've discussed in class (and many others), and lots of other techniques people have learned over the years for writing good, working, efficient, readable, modifiable programs quickly. For some of these ideas, please read my List of Adages on Software Engineering.
The precise coverage of this course changes from year to year, depending on how many students have what background. This year, about half of you have studied C++, half Java, half Scheme, one or two C, and probably none have studied Prolog. So we'll discuss all those languages at various times in class; when I'm talking about things that are old hat to you, feel free to work on your homework instead. I expect that most days in the lab will be either help-with-your-homework or "mini-lectures" in one corner of the room for those people interested in a particular topic.