There is much material about how to turn in lab assignments in this class, how to use omega, tips on writing functions, and bits of info about challenging things in C. ** USE IT.** Other material posted here includes old test materials and links outside UTA to related and useful sites. There are also links to UTA and other sites with information on the vi editor, the pico editor, on Unix systems, and OIT information.
Those lectures that have been captured to the web are linked on the lecture capture page.
Final Exam for CSE 1320 will be Tuesday, May 11th at 2pm in class.
Lab #4 Assignment for Spring 2010 as web page
Please report any errors or typos in assignment to Dr. T by e-mail ASAP.
Lab #4 DESIGN DOCUMENT DUE
Thursday, May 4th
at 1:00pm. If turning in as hardcopy, contact TA for instructions on how to submit.
See lab submission instructions below
Lab #4 Assignment for Spring 2010 as MS Word doc
Lab #4 DUE
Thursday, May 11th
at 8:00pm NO EXCEPTIONS
See lab for details about extra credit for EARLY submission.
Submit Design Document and Lab to assigned TA (see NEW info in the table below)
NOTE:
Design Documents and/or Labs turned in to Dr. T instead of assigned TA will NOT BE GRADED.
Posted 30 April 2010
Completed:
Lab #3 Assignment for Spring 2010
Lab #2 Assignment for Spring 2010
Lab #1 Assignment for Spring 2010
Pre-Lab Assignment for Spring 2010
CSE1320 Syllabus
Posted 20 Jan 2010
|
Schedule for Spring 2010
Posted Jan. 2010
|
Ethics statement
If you did not sign this in class, then print it on one page, sign, and bring to the next class |
Section:
002
Lab #4 : last names A - K
002
Lab #4 : last names L - Z
SI
TA:
Yuanzhe Cai
Dong-Chul Kim
TBD
For questions, e-mail:
caiyuanzhe_00@126.com
cse1320.2010s.kim@gmail.com
TBD
For lab submissions,
send to:
caiyuanzhe_00@126.com
cse1320.2010s.kim@gmail.com
N/A
Office Hours:
RF 10am - 12noon
MW 10am - 12noon
See
SI website, login with your UTA NetID
(put uta\ before your username if you are using an XP system)
Location:
NH 232
NH 234
See
SI website
and
then select CSE1320 from the SI Course list
How to submit your 1320 Lab - including script file info
Coding and Other Tips for Lab Assignments in CSE1320
Software Engineering Slide Presentation
Beginner's guide to writing a C function
Intro to omega
This has hints about control structures, variable types, arrays, structs, pointers, linked lists, recursion and DEBUGGING!
2nd Example Quiz with solutions
Sample Test Questions with Comments
Below is a link to the review sheets and tests that were given for previous C classes. Similar reviews will be posted for this semester.
Tests, test reviews, and old lab assignments for previous C 1320 classes taught by Dr. Tiernan
These links go to various resources for Unix, the vi editor, and the emacs editor. There is also a link to the main OIT web page for questions about UTA's systems.
"how-to" Unix reference manual from UTA OIT
vi Unix editor reference from UTA OIT
vi
Unix editor reference: University of Washington
vi
Unix editor tutorial: University of Hawaii
emacs
Unix editor reference manuals: GNU organization
pico Unix editor reference from the University of Michigan
pico Unix editor reference from the University of Chicago
OIT - Office of Information Technology website which has other helpful links
 
Updated Oct. 2008
 
Lab Assignment Submission Information for Dr. Tiernan's section of CSE 1320
Miscellaneous Coding Tidbits
To get input from data files:
Include stdio.h as a header file, declare a FILE * variable, use fopen to connect the FILE * variable to your physical file. See references further below for C file I/O examples.
To deal with reading strings correctly from files:
When reading a string after reading a number from a file, you may need to read a junk character out between reading the number and the string. Use the getc(file_pointer) command to read one character from a file. If one doesn't work try using two getc commands.
To compile multiple physical files into a single program:
To compile two files (Ex: L41.c and L42.c) together into a single
program, use the gcc command with both file names following. Example:
  myomega>gcc L41.c L42.c
To get time and date information for your program using C functions:
Information and an example using localtime(), time(), and the struct tm are available at
www.cplusplus.com/ref/ctime/localtime.html
Click on the various links to see the struct definition and other examples
Reference from Boston University CS class
C File I/O
Use section "2. C FIle I/O". Ignore section "1. Redirection".
File I/O, fopen and fclose
Clearly written with examples
Links to information about using 'getline' instead of 'gets':
GNU C Manual - Line-Oriented Input
GNU C Programming Tutorial - getline
The above link is for a Powerpoint presentation on Software Engineering that will be presented at the beginning of the semester.
Covers how to connect to omega, a few Unix commands, a short list of editors and compilers and an example of using the GDB debugger which is available for gcc.
A Powerpoint presentation by Do Kim (CSE senior) edited by Dr. T.
Posted 31 August 2004
Sticky Bits in C online presentation
Sticky Bits in C to download
A Powerpoint presentation by Dr. T.
Posted 19 April 2004
- be sure to scroll down to the bottom of the OIT page if no Unix guide
info is visible to the right of the menu bar
- be sure to scroll down to the bottom of the OIT page if no vi editor
info is visible to the right of the menu bar