New User Special Price Expires in

Let's log you in.

Sign in with Facebook


Don't have a StudySoup account? Create one here!


Create a StudySoup account

Be part of our community, it's free to join!

Sign up with Facebook


Create your account
By creating an account you agree to StudySoup's terms and conditions and privacy policy

Already have a StudySoup account? Login here

Systems Prog Concpts

by: Lisette Hodkiewicz

Systems Prog Concpts CS 2240

Lisette Hodkiewicz
GPA 3.83

Robert Trenary

Almost Ready


These notes were just uploaded, and will be ready to view shortly.

Purchase these notes here, or revisit this page.

Either way, we'll remind you when they're ready :)

Preview These Notes for FREE

Get a free preview of these Notes, just enter your email below.

Unlock Preview
Unlock Preview

Preview these materials now for free

Why put in your email? Get access to more of this material and other relevant free materials for your school

View Preview

About this Document

Robert Trenary
Class Notes
25 ?




Popular in Course

Popular in ComputerScienence

This 2 page Class Notes was uploaded by Lisette Hodkiewicz on Wednesday September 30, 2015. The Class Notes belongs to CS 2240 at Western Michigan University taught by Robert Trenary in Fall. Since its upload, it has received 68 views. For similar materials see /class/216874/cs-2240-western-michigan-university in ComputerScienence at Western Michigan University.

Similar to CS 2240 at WMU

Popular in ComputerScienence


Reviews for Systems Prog Concpts


Report this Material


What is Karma?


Karma is the currency of StudySoup.

You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!

Date Created: 09/30/15
C8224 Spring 20088 Source Style Guidelines DRAFT This is only a draft version ofthis document Over time it will be expanded and revised Introduction and Rationale The purpose of this document is to provide a short guideline for the stylistic aspects of c It outlines what I consider to be good programming style as such it is a guideline for how to write good code code that will be graded favorably I try to make these guidelines as general as possible I do not want to force you to follow my style for writing code rather I want you to follow your own style provided that your style is consistent and follows basic rules about what is good code and what isn t Some of these guidelines are concerned with solely syntactical matters comments laying out code etc These obviously do not affect how your program runs but rather affect how it appears to a human reader of the code Other guidelines do involve the flow of execution It is important to remember that when writing code in a job you can expect many programmers to modify your code after you have finished with it fixing bugs extending it etc Their job will be made easier if you write better code And you can also expect your employers to have their own ideas about what constitutes good code probably in more strict terms than what you see here You should view your code as a paper written for a literature course Your program working correctly is analogous to a paper that gets its idea across and has good ideas But you would never consider turning in a paper with poor grammer spelling mistakes and unclear and wandering prose Similarly you should not turn in a programming assignment with code that is unclear The code should be formatted indented and commented correctly Variables and functions should have their names chosen with care And the overall design ofthe code should be logical and modular Code Formatting Code formatting involves the general appearance of the code white space indenting etc Guidelines Code should have a consistent indentation Generally subblocks of code bodies of if statements for loops etc should be indented some fixed number of columns from the higher level block While you are free to choose the details number of characters to indent placement of braces etc you should aim for a consistent look across all your code mments should be indented to the same depth as the code they explain When printing out your code make sure that lines do not get truncated at the right side ofthe paper Generally I find it easier to pick a maximum line length based on the paper on which I will be printing and my computereditor combination and then rigorously chop off all lines of code before that length is reached The remaining portion ofthat line of code should then appear as the next line ofthe source file properly indented Commenting This section contains guidelines for the proper placement and content of comments There are some fairly explicit guidelines for including comments read and follow them carefully as they are the basis for some of the grading for the assignments Guidelines Each source file and header file in your assignment should have a block comment at the top This comment should identify the source file by name provide a brief description of the contents of the source file possibly identify the project for which the source file was written eg the assignment for which the assignment was written the author and the creation date recommend creating a template of this block comment and then copy it into each new source file you create and then fill in the blanks Note to Emacs users C x iwill insert a file into the current buffer or use C x C f to load the template file and then Cx C w to save it under a new name Or explore the filenotfoundhook for automatic insertion of text by file name into a buffer when a new file is not found Each function and macro should have a comment at the top This comment should explain what the function does It should also identify and explain each parameter including whether the parameter is an IN and OUT or an lNOUT parameter Any unusual preconditions or sideeffects of the function should be explained In general comments should explain the code not echo what the code does If you find yourself writing a line of comments for each line of code your comments are probably just repeating the code


Buy Material

Are you sure you want to buy this material for

25 Karma

Buy Material

BOOM! Enjoy Your Free Notes!

We've added these Notes to your profile, click here to view them now.


You're already Subscribed!

Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'

Why people love StudySoup

Bentley McCaw University of Florida

"I was shooting for a perfect 4.0 GPA this semester. Having StudySoup as a study aid was critical to helping me achieve my goal...and I nailed it!"

Kyle Maynard Purdue

"When you're taking detailed notes and trying to help everyone else out in the class, it really helps you learn and understand the I made $280 on my first study guide!"

Steve Martinelli UC Los Angeles

"There's no way I would have passed my Organic Chemistry class this semester without the notes and study guides I got from StudySoup."

Parker Thompson 500 Startups

"It's a great way for students to improve their educational experience and it seemed like a product that everybody wants, so all the people participating are winning."

Become an Elite Notetaker and start selling your notes online!

Refund Policy


All subscriptions to StudySoup are paid in full at the time of subscribing. To change your credit card information or to cancel your subscription, go to "Edit Settings". All credit card information will be available there. If you should decide to cancel your subscription, it will continue to be valid until the next payment period, as all payments for the current period were made in advance. For special circumstances, please email


StudySoup has more than 1 million course-specific study resources to help students study smarter. If you’re having trouble finding what you’re looking for, our customer support team can help you find what you need! Feel free to contact them here:

Recurring Subscriptions: If you have canceled your recurring subscription on the day of renewal and have not downloaded any documents, you may request a refund by submitting an email to

Satisfaction Guarantee: If you’re not satisfied with your subscription, you can contact us for further help. Contact must be made within 3 business days of your subscription purchase and your refund request will be subject for review.

Please Note: Refunds can never be provided more than 30 days after the initial purchase date regardless of your activity on the site.