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. A quick link to a page of Dr. T's helpful C stuff [This is USEFUL stuff! Check it out!]
Those lectures that have been captured to the web are linked on the lecture capture page.
Final Exam is in class Tuesday August 16 at 1:00pm
All material covered in lectures, in textbook for chapters covered in lectures, or required to have completed Labs 1 - 4 may be covered on the test.
Read your textbook and bring it to class!
Please report any errors or typos in assignment to Dr. T by e-mail ASAP.
Please report any errors or typos in assignment to Dr. T by e-mail ASAP.
NOTE: Lab #3 had typo in DEDUCTIONS section stating that "structs" would be a deduction. This is an error. You MUST use structs in the Lab3. The deduction is only for using linked lists in Lab #3. (Thanks to the two folks who pointed this out.)
Please report any errors or typos in assignment to Dr. T by e-mail ASAP.
Please report any errors or typos in assignment to Dr. T by e-mail ASAP.
Lab #4 Assignment for Summer 2011
as an ugly
web page and
as
MS Word doc. Grading scale has been added.
Lab #4 Design Document must be submitted on time in order for
Lab #4 assignment to be graded.
Submit
Design Document to assigned TA (see info in the table below)
Contact Dr. T in case of problems.
Extra credit for early submission as follows:
Early submission by 11:59pm Wednesday August 17 + 8 points
Early submission by 11:59pm Tuesday August 16 + 18 points
Early submission by 11:59pm Monday August 15 + 30 points
Early submission by 11:59pm Sunday August 14 + 42 points
NO LATE LABS accepted for Lab #4 period.
Submit
Lab to assigned TA (see info in the table below)
See lab submission instructions below
Posted July 30
Lab #3 Assignment for Summer 2011
as
web page
and as
MS Word doc
Lab #3 Design Document must be submitted on time in order for
Lab #3 assignment to be graded.
Submit
Design Document to assigned TA (see info in the table below)
Contact Dr. T in case of problems.
No late labs accepted without special permission from Dr. Tiernan.
Submit
Lab to assigned TA (see info in the table below)
See lab submission instructions below
Posted July 12
Lab #2 Assignment for Summer 2011
as
web page
and as
MS Word doc
Lab #2 Design Document must be submitted on time in order for
Lab #2 assignment to be graded.
Submit
Design Document to assigned TA (see info in the table below)
Contact Dr. T in case of problems.
No late labs accepted without special permission from Dr. Tiernan.
Submit
Lab to assigned TA (see info in the table below)
See lab submission instructions below
Posted June 21
Lab #1 Assignment for Summer 2011
will have three parts. Parts I and II are given here and Part III will posted soon. Parts I and II are available
as
web page
and as
MS Word doc
Just added
Part III is available
as
web page
and as
MS Word doc
No late labs accepted without special permission from Dr. Tiernan.
Submit
Lab to assigned TA (see info in the table below)
See lab submission instructions below
Posted June 7; part 3 posted June 11
|
CSE1320 Syllabus
CSE1320 Syllabus Word doc Posted 7 June 2011
|
To be posted |
Ethics statement
If you did not sign this in class, then print it on one page, sign, and bring to the next class |
If you have trouble reading something on this website or
Section:
Section 001 - Dr. Tiernan
Section 001 - Dr. Tiernan
CSE Help Desk
TA:
Mehra Nouroz Borazjany
Shiraz Qayyum
Various
For questions, e-mail:
mehra.nourozborazjany@mavs.uta.edu
shiraz.qayyum@mavs.uta.edu
N/A
For lab submissions,send to:
cse1320summer@gmail.com
cse1320summer@gmail.com
N/A
Office Hours:
After July 1, Tues and Fri 11am - 12:30pm, ERB 503
Tues and Thurs 10:30am - 12noon, ERB 560
TBD
Location:
ERB 503 (the new Engineering Research Building)
ERB 560 (the new Engineering Research Building)
ERB 132 (The new Engineering Research Building)
Miscellaneous Coding Tidbits
Software Engineering Slide Presentation
Intro to omega
This has hints about control structures, variable types, arrays, structs, pointers, linked lists, recursion and DEBUGGING!
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.
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
Reference material for Lab Assignments
How to submit your 1320 Lab - including script file info
Updated Dec. 2010
Lab Assignment Submission Information for Dr. Tiernan's section of CSE 1320
Links to information about using 'getline' instead of 'gets':
GNU C Manual - Line-Oriented Input
GNU C Programming Tutorial - getline
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
Coding and Other Tips for Lab Assignments in CSE1320
Dr. Brezeale's handy-dandy notes on moving from Python to C (see the Misc. section)
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
CSE1320 Powerpoint presentations
The above link is for a Powerpoint presentation on Software Engineering that will be presented at the beginning of the semester.
Beginner's guide to writing a C function
Reference card for C commands to keep handy while you start writing functions
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
Reference card for UNIX commands to use on omega
Sticky Bits in C online presentation
Sticky Bits in C to download
A Powerpoint presentation by Dr. T.
Posted 19 April 2004
"how-to" Unix reference manual from UTA OIT
- 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