Information for CSE1320
Intermediate Programming with C

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 is Mon. Aug. 16th at 10:30am in class. Open book, open notes, no electronics.

     Lab #4 C++ Assignment for Summmer 2010 as web page and as MS Word doc

            Lab #4 DESIGN DOCUMENT DUE Wednesday, August 11 at 10:00am. If turning in as hardcopy, contact TA for instructions on how to submit.
            Submit Design Document and Lab to assigned TA (see info in the table below)

            Lab #4 DUE Tuesday, August 17th at 8:00pm
            NO EXCEPTIONS
            See lab for details about extra credit for EARLY submission.
            Posted 5 August 2010;

Misc. Handy C++ stuff for this lab:
A) Dr. T continues to incorrectly say and write gpp for the compiler name - it is g++ .
B) In your file containing main make sure you #include the iostream file and that you have the line
      using namespace std;
after the #includes to make C++ work well.
C) For purposes of Lab #4 you can continue to use C strings and string functions. Just make sure you include the correct library files for those functions.
D) To use an input file with C++ takes the following steps:
      1) at the top use #include < fstream.h > or just fstream without .h
      2) declare an input file stream object, connect it to a physical file, and open the file by a declaration like the following:
            ifstream infile("lab4data.dat");
      where ifstream is the input file stream class type, infile is the object, i.e. variable, name, and "lab4data.dat" is the name of a file that you want to use for the input file. Notice that this declaration does the equivalent of both declaring a FILE * variable and doing an fopen command in C. Now you should be able to use the infile object anywhere that you would use the cin object. You may choose your own object variable name. You should use the same input file as for Lab #3.
E) To check for the end of a file in C++ you test infile.eof(). This returns true if the file is at the end. Note that infile is the file stream object referred to in part D) above.

---

     Lab #3 Assignment for Summmer 2010 as web page and as MS Word doc

            Lab #3 DUE Friday, August 6th at 10:00am
            Please report any errors or typos in assignment to Dr. T by e-mail ASAP.

            See lab submission instructions below
            Posted 26 July 2010;

Completed:
Pre-Lab Assignment for Summmer 2010
Lab #1 Assignment for Summmer 2010
Lab #2 Assignment for Summmer 2010

CSE1320 Syllabus CSE1320 Syllabus Word doc Posted 6 June 2010

Schedule for Summer 2010 TBD Posted June 2010

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
if you find a broken link or other problem
please e-mail Dr. Tiernan

Section:	001 Lab #3 : last names M - Z Lab #4 : last names A - L	001 Lab #3 : last names A - L Lab #4 : last names M - Z	SI
TA:	Yuanzhe Cai	Dong-Chul Kim	TBD
For questions, e-mail:	caiyuanzhe_00@126.com	cse1320.kim@gmail.com	TBD
For lab submissions, send to:	caiyuanzhe_00@126.com	cse1320.kim@gmail.com	N/A
Office Hours:	TU, TH 1pm - 3pm	TU, TH 10am - 12 noon	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

Reference material for Lab Assignments

How to submit your 1320 Lab - including script file info
     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

Coding and Other Tips for Lab Assignments in CSE1320

Links to information about C file I/O:
Reference from Boston University CS class
C File I/O
Use section "2. C FIle I/O". Ignore section "1. Redirection".

Reference from University of Essex
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

CSE1320 Powerpoint presentations

Software Engineering Slide Presentation
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

Intro to omega
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

This has hints about control structures, variable types, arrays, structs, pointers, linked lists, recursion and DEBUGGING!
Sticky Bits in C online presentation
Sticky Bits in C to download
A Powerpoint presentation by Dr. T.
Posted 19 April 2004

Example Quiz

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

Example Ethics Policy

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
   - 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

   vi Unix editor reference from UTA OIT
   - 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

   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

Copyright Tyger Design, Inc. Web page created by Tyger Design.