Lab46 Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
<WRAP centeralign round box>
<WRAP><color red><fs 200%>Corning Community College</fs></color></WRAP>
<WRAP><fs 150%>CSCS2320 Data Structures</fs></WRAP>
</WRAP>

~~TOC~~

======Project: DATA TYPES======

=====Objective=====
To familiarize yourself with the available data types in C- the variations, the attributes, the ranges therein.
=====Prerequisites=====
In order to successfully accomplish/perform this project, the listed resources/experiences need to be consulted/achieved:

  * ability to log into Lab46
  * ability to change to course-specific source directory
  * ability to edit text files
  * ability to compile C source code
  * ability to read and appropriately react to compiler messages during compilation
  * ability to execute compiled code
  * knowledge of the size of a byte, how many bit combinations are possible therein
  * ability to use version control system to track created source file(s)

=====Scope=====
This project will be exploring the nature of some of the data types available to us in the C Programming Language. How much space is allocated to each type, how many numbers can exist within each type, and what are the ranges available for each type?

A program will be written that will display (to STDOUT) the size (in bytes), the lower and upper bounds of each studied type, and (as accurately as possible) display the total quantity of values possible with each type.

The data types covered for this project will include **signed** and **unsigned** variations of:

  * char
  * short int
  * int
  * long int
  * long long int

The **sizeof()** and **printf()** functions, as well as arithmetic and logical operators, will be utilized in performing much of the work.

=====Code=====

====Skeleton Program====
Here is the skeleton of a program you'll want to use for this project:

<code c>
/*
 * datatypes.c - A program to derive and display information
 *               for the signed and unsigned data types in C
 *
 *
 * A program by NAME for CSCS1320 COURSE (SEMESTER)
 *
 * Compile with: gcc -o datatypes datatypes.c
 * Execute with: ./datatypes
 */
 
#include <stdio.h>
 
int main()
{
    // Variables
    unsigned char uchr = 0;
    
    // Code for unsigned char
    
    // Code for signed char
    
    // Code for unsigned short int
    
    // Code for signed short int
    
    // Code for unsigned int
    
    // Code for signed int
    
    // Code for unsigned long int
    
    // Code for signed long int
    
    // Code for unsigned long long int
    
    // Code for signed long long int
 
    return(0);
}
</code>

====unsigned char code block====
Following is provided code giving you the requested information for an **unsigned char**. Study it, implement it, and adapt it as needed to the other data types:

<code c>
    // Code for unsigned char
    fprintf(stdout, "TYPE: %13s, ", "unsigned char"); // What is happening here?
    fprintf(stdout, "bytes: %lu, ", sizeof(uchr));    // Why does sizeof() need %lu?
    fprintf(stdout, "low: %hhu, ",  (uchr & 0x00));   // Why 2 zeros?
    fprintf(stdout, "high: %hhu, ", (uchr | 0xFF));   // Why 2 F's?
    uchr = uchr - 1;                                   // What does this line do?
    fprintf(stdout, "qty: %hu\n",   (uchr+1));        // What is going on here?
</code>

Note that by adapting, you'll need to declare and initialize additional variables, and you may "unroll" some of the logic here to do it in more discrete steps (in fact, it may enable you to solve a couple problems that crop up).
=====Execution=====

<cli>
lab46:~/src/data$ ./datatypes
TYPE: unsigned char, bytes: 1, low: 0, high: 255, qty: 256
TYPE:   signed char, bytes: X, low: X, high: X, qty: X
TYPE: unsigned short int, bytes: X, low: X, high: X, qty: X
TYPE:   signed short int, bytes: X, low: X, high: X, qty: X
...
lab46:~/src/data$ 
</cli>

This output includes some mock additional entries, actual values abstracted. Instead of displaying 'X', your program should display the actual values, and display a total of 10 lines, for the signed and unsigned variations of the five data types we are studying in this project.
=====Reflection=====
Be sure to provide any commentary on your opus regarding realizations had and discoveries made during your pursuit of this project.

Also, answer the following questions:

  * What two data types appeared "the same"?
    * Why may this may be?
    * Is this universal for all systems, or just a certain subset?
  * With respect to **printf()**:
    * What is the difference between **printf()** and **fprintf()**?
    * What is **stdout**? Where is it by default?
    * What is the difference between **%s**, **%hhu**, **%hu**?
    * How about **%u** and **%d**?
    * What does the **13** in **%13s** do for us?
  * If sign was left unspecified, which state is assumed by default?
  * What are the **<nowiki>&</nowiki>** and **<nowiki>|</nowiki>** operators?
    * How did they help you achieve the solution?
  * If you experienced trouble displaying the total quantity for a certain type, why was this?
  * Based on your program's output, what are the total **bits** allocated for:
    * signed char
    * unsigned short int
    * unsigned int
    * signed int
    * signed long long int

=====Submission=====
To successfully complete this project, the following criteria must be met:

  * Code must compile cleanly (no warnings or errors)
  * Executed program must display a total of 10 lines, one for each data type.
  * Output must be correct, and in its simplest/most reduced form (based on available resources)
    * Each type must show a mathematically correct quantity
    * high and low values **must** be computed logically
  * Code must be nicely and consistently indented (you may use the **indent** tool)
  * Code must be commented
    * have a properly filled-out comment banner at the top
    * have at least 20% of your program consist of **<nowiki>//</nowiki>**-style descriptive comments
  * Output Formatting (including spacing-- overall field alignment is not needed) of program must conform to the provided output (see unsigned char example above).
  * Track/version the source code in a repository
  * Submit a copy of your source code to me using the **submit** tool.

To submit this program to me using the **submit** tool, run the following command at your lab46 prompt:

<cli>
$ submit data datatypes datatypes.c
Submitting data project "datatypes":
    -> datatypes.c(OK)

SUCCESSFULLY SUBMITTED
</cli>

You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.
Lab46 Wiki

User Tools

Site Tools

Page Tools
