<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="serif">This is in the syllabus....</font></p>
<p><br>
</p>
<div style="left: 101.512px; top: 139.047px; font-size: 16.6043px;
font-family: sans-serif; transform: scaleX(0.874585);"><b><font
size="+1">Honor Code:</font></b><br>
<br>
</div>
<div style="left: 101.512px; top: 158.973px; font-size: 16.6043px;
font-family: sans-serif; transform: scaleX(0.881375);">All
students in CSC 315 are expected to adhere to the Mercer
University Honor Code. Any suspected violations will be reported
to the Honor Council for further investigation.<br>
<br>
</div>
<div style="left: 101.512px; top: 205.465px; font-size: 16.6043px;
font-family: sans-serif; transform: scaleX(0.869757);">Many
students have difficulty in determining how to apply the Mercer
honor code to computer courses. A fewgeneral guidelines should
help you in deciding whether you are violating the honor code or
not.<br>
<br>
</div>
<div style="left: 138.04px; top: 394.755px; font-size: 16.6043px;
font-family: sans-serif; transform: scaleX(0.851765);">1. You are
allowed to receive help on your programs from other students,
provided the purpose of the help is to foster your understanding
of your own program better, not to write your program for you.<br>
2. You are NOT allowed to use copies of programs written by other
students, or copies of programs from published sources, even if
you plan to modify them extensively. The only exception to this
rule is when the instructor provides you with code that should be
incorporated into your program. In such cases the code must
clearly be set off and the source or the code noted in the
program.<br>
3. You are NOT allowed to give copies of your programs, or parts
of your programs, to other students in any form.<br>
<br>
</div>
<div style="left: 138.04px; top: 461.173px; font-size: 16.6043px;
font-family: sans-serif; transform: scaleX(1.03759);">
<blockquote>
<blockquote>
<blockquote>4. YOU MUST WRITE YOUR OWN CODE. DO NOT COPY
PROGRAMS OR PARTS OF PROGRAMS FROM ANY SOURCE UNLESS I TELL
YOU TO DO SO. IF YOU USE CODE I GAVE YOU PLEASE NOTE THE
LOCATION OF THIS CODE IN YOUR PROGRAM VIA COMMENTS.<br>
</blockquote>
</blockquote>
</blockquote>
<br>
</div>
<div style="left: 101.512px; top: 497.703px; font-size: 16.6043px;
font-family: sans-serif; transform: scaleX(0.894832);">Any
violation of the above policies will be treated as academic
dishonesty and a violation of the Mercer Honor</div>
<div style="left: 101.512px; top: 517.628px; font-size: 16.6043px;
font-family: sans-serif; transform: scaleX(0.893101);">Code.</div>
<p><br>
</p>
<p>I am noticing in some repos a tendency to use a certain makefile
example from the internet that uses "wildcards" and a subdirectory
structure in a creative way, but that also generates other
problems. What troubles me is that it is not something I gave you
and it is being used used amongst several of you. I dare say if
I asked you how the particular makefile worked, very few of you
using it would be able to explain what the symbols and commands in
the makefile do -- or why you have all kinds of superfluous and
unused function definitions in a library that you are building in
one of those subdirectories. What would happen if I asked you to
explain those undocumented functions and libraries that just
magically appeared across several of your repositories. <br>
</p>
<p>You have been warned...<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Andrew J. Pounds, Ph.D. (<a class="moz-txt-link-abbreviated" href="mailto:pounds_aj@mercer.edu">pounds_aj@mercer.edu</a>)
Professor of Chemistry and Computer Science
Mercer University, Macon, GA 31207 (478) 301-5627
<a class="moz-txt-link-freetext" href="http://faculty.mercer.edu/pounds_aj">http://faculty.mercer.edu/pounds_aj</a>
</pre>
</body>
</html>