-
Notifications
You must be signed in to change notification settings - Fork 484
/
readme-old.html
266 lines (266 loc) · 14 KB
/
readme-old.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>Program and Data Representation</title>
<style>
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
<link rel="stylesheet" href="markdown.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<h1 id="program-and-data-representation">Program and Data
Representation</h1>
<p><a href="#introduction">Introduction</a> | <a
href="#contents">Repository contents</a> | <a
href="#contributing">Contributing to this repository</a> | <a
href="#description">Course description</a> | <a
href="#markdown">Markdown</a> | <a href="#sourcecode">Source code</a> |
<a href="#canvasnotes">Canvas notes</a> | <a
href="#license">License</a></p>
<h2 id="introduction"><a name="introduction"></a>Introduction</h2>
<p>This repository contains the materials for the course entitled “CS
2150: Program and Data Representation” in the <a
href="http://www.cs.virginia.edu">Computer Science Department</a> at the
<a href="http://www.virginia.edu">University of Virginia</a>. It
contains all of the slides, labs, exams, etc., used throughout the
course. The course description is <a href="#description">below</a>. The
github repository for this course is at <a
href="https://github.com/markfloryan/pdr">https://github.com/markfloryan/pdr</a>.</p>
<p>Students <em>currently</em> in the course should view the <a
href="uva/index.html">uva/index.html</a> (<a href="uva/index.md">md</a>)
file in the <strong>cloned</strong> repository (i.e., don’t try to view
it on github.com); current students may also want to view the <a
href="uva/daily-announcements.html#/">daily announcements</a>. Note that
many of the course materials are modified right before they are needed –
for example, this repository will be updated right before the semester
starts.</p>
<p>Students who were previously in the course may want to view the
current version, or you can view the version from your semester. All
semester versions are tagged with an end-of-semester tag of the form
“year-semester”. For example, the spring 2014 semester was tagged as
<code>2014-spring</code>. To obtain a specific tag, you can enter
<code>git checkout tags/2014-spring</code> in an already cloned
repository.</p>
<p>The primary author of this repository is <a
href="http://www.cs.virginia.edu/~mrf8t">Mark Floryan</a> (<a
href="mailto:mrf8t@cs.virginia.edu">mrf8t@cs.virginia.edu</a>). This
repository originally developed (and has been adapted from) a similar
one by <a href="http://www.cs.virginia.edu/~asb">Aaron Bloomfield</a>
(<a href="mailto:aaron@virginia.edu">aaron@virginia.edu</a>. Many
students and faculty have worked on this course material over the
years.</p>
<h2 id="repository-contents"><a name="contents"></a>Repository
Contents</h2>
<p><strong>Note that the links below will not work correctly if you are
viewing this online at github.com – you will need to clone (download)
the repository first</strong></p>
<ul>
<li><a href="book/index.html">book</a> (<a href="book/index.md">md</a>):
the beginnings of a textbook to be used for this course. It is written
using LaTeX.</li>
<li><a href="docs/index.html">docs</a> (<a href="docs/index.md">md</a>):
a series of useful documents that are not labs or tutorials.</li>
<li><a href="uva/index.html">uva</a> (<a href="uva/index.md">md</a>):
the materials that are specific to CS 2150 as taught at the University
of Virginia, such as daily announcements, due dates, etc.</li>
<li><a href="exams/index.html">exams</a> (<a
href="exams/index.md">md</a>): past exams for the course; there are two
midterms and a final for each semester.</li>
<li><a href="ibcm/ibcm.html">ibcm</a> (<a href="ibcm/ibcm.md">md</a>):
the files necessary for the IBCM module on machine language, which is
taught about two thirds of the way into the course.</li>
<li><a href="labs/index.html">labs</a> (<a href="labs/index.md">md</a>):
the labs are the main assignments in the course, and each lab is split
into pre-lab, in-lab, and post-lab parts. There are 11 full labs, with a
partial 12th lab that is an optional component of the course. The labs
are written using <a
href="http://daringfireball.net/projects/markdown/">markdown</a>, and
the rendered HTML version of each lab is also committed to this
repository.</li>
<li><a href="slides/index.html">slides</a> (<a
href="slides/index.md">md</a>): Contains the slides used in the course.
The slides use <a
href="https://github.com/hakimel/reveal.js/">reveal.js</a>, an HTML
presentation framework.</li>
<li><a href="tutorials/index.html">tutorials</a> (<a
href="tutorials/index.md">md</a>): the tutorials that are used as part
of the lab assignments, these are primarily Linux tutorials.</li>
<li><a href="utils/index.html">utils</a> (<a
href="utils/index.md">md</a>): various utilities for this
repository</li>
</ul>
<h2
id="contributing-to-this-repository"><a name="contributing"></a>Contributing
to this Repository</h2>
<p>Updates to the repository are restricted to approved individuals
only, to prevent anybody from messing with the slides right before a
lecture. However, others can still contribute to this repository – to do
so, take the following steps:</p>
<ol type="1">
<li>Create a github account, if you do not have one</li>
<li>Fork this repository: you can click on the “Fork” link in the upper
right, or just click <a
href="https://github.com/markfloryan/pdr/fork">here</a></li>
<li>Clone your forked repository on to your local machine</li>
<li>Make any changes you want to your forked version, then commit and
push your changes back to your forked repository</li>
<li>Create a pull request, following the instructions <a
href="https://help.github.com/articles/creating-a-pull-request">here</a></li>
</ol>
<p>At that point, I will receive a notice that a change has been
submitted, and I’ll look at it and hopefully accept it into the main
repository.</p>
<p>When you want to bring in the updates from the main pdr github
repository into your forked repository, you will need to follow the
instructions <a
href="https://help.github.com/articles/syncing-a-fork">here</a>.</p>
<h2 id="course-description"><a name="description"></a>Course
Description</h2>
<p>This course is a second-year course for computer science majors. It
is the primary data structures course in the <a
href="http://www.virginia.edu">University of Virginia</a>’s <a
href="http://www.cs.virginia.edu">computer science</a> curriculum.
Unlike many other data structure courses at other institutions, it is
intended as the <em>third</em> course in sequence, meaning that students
are expected to have taken two semesters of Java (or equivalent,
although some of the examples are specifically from Java). The course
focuses on how programs and data are represented from the high level
down to the low level. For programs, we examine (from high to low):
abstract data types, Java code, C++ code, C code, assembly (x86) code,
and a customized machine language. For data, we examine (also from high
to low): abstract data types, objects, primitive types, and how numbers
are encoded (both floats (IEEE 754) and integers (two’s complement)).
About two-thirds of this course is programming using C++. The remainder
of this course uses other languages, including (in decreasing order):
x86 assembly, IBCM (a machine language), C, Objective C, and shell
scripting.</p>
<p>The <a href="http://www.abet.org">ABET</a> course objects are as
follows:</p>
<ul>
<li>Understand program representation from the high-level programming
language perspective down to the underlying machine level
representation, including: number representation, operations,
conditionals, and control structures</li>
<li>Be able to implement basic and advanced abstract data types in C++
including: linked lists, stacks, queues, hash tables, trees, and
graphs</li>
<li>Be able to evaluate asymptotic time and space complexity analysis of
programs and data structure implementations using Big-O, Big-Omega, and
Big-Theta notation and assess the suitability of a data structure for a
particular problem</li>
<li>Understand the basic program execution model and the underlying
computer hardware and software (fetch-execute cycle, memory hierarchy,
operating system, compiler)</li>
<li>Be able to implement basic program control and data structures in an
assembly language (loops, conditionals, subroutines and parameter
passing modes, arrays)</li>
</ul>
<h2 id="markdown"><a name="markdown"></a>Markdown</h2>
<p>The majority of the content in this repository was created using <a
href="http://daringfireball.net/projects/markdown/">Markdown</a>.
Unfortunately, the only standardized Markdown is very old (2004), and
has limited support for many HTML features, such as tables. In the past,
there were custom utilities (which can still be found in the <a
href="utils/index.html">utils</a> (<a href="tutorials/index.md">md</a>)
directory) were used. However, <a
href="http://johnmacfarlane.net/pandoc/">pandoc</a> is now used (which
is installed via the “pandoc” package on Ubuntu). Typing
<code>make</code> in the root repo directory will call pandoc on all the
markdown files.</p>
<p>For all the Markdown files in this repository, both the original
(.md) file and the HTML version (.html) are added to the repository, so
that people who do not have Markdown installed can still view the
contents of this repository.</p>
<p>Note that Github supports an enhanced version of Markdown, called <a
href="https://help.github.com/articles/github-flavored-markdown">Github
Flavored Markdown</a>, or GFM. This mostly pertains to this README file.
In an effort to ensure compatibility with other Markdown programs (such
as the one described here and what reveal.js uses), GFM specific
features are generally avoided. One example is the use of anchors in
this document – the HTML tags are included instead of using GFM’s
version.</p>
<h2 id="source-code"><a name="sourcecode"></a>Source code</h2>
<p>All source code is formatted via <a
href="http://astyle.sourceforge.net/">astyle</a> and then highlighted
via <a
href="http://www.gnu.org/software/src-highlite/source-highlight.html">source-highlight</a>.
Both the original file (foo.cpp) and the highlighted version
(foo.cpp.html) are included in the repository. All links to source code
will like to the .html, with a “(<a href="README.md">src</a>)” after it
to link to the original source code.</p>
<ul>
<li>astyle options: <code>-A2 -s4 -S</code></li>
<li>source-highlight options: <code>-d</code></li>
</ul>
<h2 id="canvas-notes"><a name="canvasnotes"></a>Canvas notes</h2>
<p>Some of the slides allow pen-based markup of the slides. To add a
canvas to a slide (to allow drawing with a mouse or a stylus), you must
do a few things:</p>
<ol type="1">
<li><p>The slide can NOT be Markdown, it must be all pure HTML</p></li>
<li><p>Include the js/canvas.js and css/dhtmlwindow.js scripts, as well
as the dhtmlwindow.css CSS file (the two dhtmlwindow.* files are for the
calibration feature):</p></li>
</ol>
<pre><code><script type="text/javascript" src="js/dhtmlwindow.js"></script>
<script type="text/javascript" src="js/canvas.js"></script>
<link rel="stylesheet" href="css/dhtmlwindow.css" type="text/css"></code></pre>
<ol start="3" type="1">
<li><p>Add an <code>onload="canvasinit()"</code> to the
<code><body></code> tag: <code><body
onload="canvasinit()"></code></p></li>
<li><p>Add the following immediately after the <code><body></code>
tag (this is for the calibration feature):</p></li>
</ol>
<pre><code><div id="dhtmlwindowholder"><span style="display:none"></span></div></code></pre>
<ol start="5" type="1">
<li>Add the following code at the end of the .html file (just before the
three script tags):</li>
</ol>
<pre><code><div id="calibratediv" style="display:none">
<div id="calibratecanvasdiv">
<canvas id="calibratecanvas" width="300" height="300">Your
browser does not support the canvas tag</canvas>
</div>
<p style="text-align:center">Click the center of the target<br><a href="#"
onClick="calibratewin.close(); return false">Close window</a></p>
</div></code></pre>
<ol start="6" type="1">
<li>Then, on each slide that you want a canvas on, you add the
following:</li>
</ol>
<pre><code><script type="text/javascript">insertCanvas();</script></code></pre>
<p>A few other notes:</p>
<ul>
<li>The canvas is larger than the slide itself, and the amount, in
number of pixels, is the <code>canvas_border</code> variable in the
canvas.js file</li>
<li>To add colors, add them to the <code>colors</code> array in the
canvas.js file; more color names can be found <a
href="http://www.tutorialspoint.com/html5/html5_color_names.htm">here</a></li>
</ul>
<h2 id="license"><a name="license"></a>License</h2>
<p>The material in this repository is released under a <a
href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons
Attribution-ShareAlike 4.0 International License</a> (CC BY-SA).</p>
<p>Copyright (c) 2017-2018 by Mark Floryan Copyright (c) 2013-2017 by
Aaron Bloomfield.</p>
<p>Some parts of this repository are taken, with permission, from other
sources. The full details are in the <a href="LICENSE.html">License</a>
(<a href="LICENSE.md">md</a>) file. In particular, some parts of this
repository that were obtained elsewhere can not be used for commercial
purposes.</p>
</body>
</html>