Course Description | This course is an in-depth introduction to C programming and Unix. C programming topics include single and multi-dimensional arrays; pointers; dynamic memory allocation and dynamic data structures such as lists and trees; and bit manipulation. Unix topics include debuggers; makefiles; shell programming; profiling and performance tuning; and other topics that support C programming. This course has a heavy programming load. See the syllabus for a tentative list of topics that will be covered. The prerequisites are CSc 127b or 227; 252 (co-requisite). |
Meeting Times | MWF 3:00-4:30 PM, BIOSCI-W 219 |
Textbooks |
|
Instructor |
Cesim Erten Office: Gould-Simpson 710E; phone: 621-4215 Office Hours: T 1.00-5.00 (in GS710E), Tr 1.00-5.00(in GS228) cesim@cs.arizona.edu |
Teaching Assistant |
Annamalai Subramanian malai@cs.arizona.edu
|
Grading | Grades will be based on the midterm exam (10%), the final exam (15%), and the assignments (75%). Late assignments will not be accepted. Without prior arrangements, missed exams result in a grade of zero. The instructor reserves the right to fail for the course any student failing the final comprehensive exam. |
Attendance | Attendance will be expected, but not recorded. Students are fully responsible for all material presented or assigned in class. For this reason, attendance is strongly recommended. |
Academic Integrity |
For the purposes of this course, cheating is considered to be
any attempt to pass off someone else's work as one's own.
(See also
UofA Code of Academic
Integrity.)
It is permissible to use ``publicly visible'' code -- code that is available in books or magazines, or which has been distributed in class -- in programming assignments, as long as the authorship of such code is adequately and explicitly acknowledged. It is not permissible to solicit code from others, e.g., by posting requests to Usenet newsgroups. Cheating will not be tolerated: any student caught cheating or helping another student cheat in homeworks, exams, or programming assignments, will be given a failing grade in the course. I intend to interpret the phrase ``helping another student cheat'' broadly: for example, if another student gains access to your code because you forgot to logout, or were careless about listings that were dumped into the recycling bin, you have helped that student cheat. |
Tutorials |
Online Documentation and Tutorials Coding Guidelines |
Announcements | cs.course352 newsgroup |