1
0

README 5.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145
  1. In this assignment, we will read a file full of integers, sort them,
  2. and then search for particular values. You will do this by editing the
  3. file "answer03.c". You should not edit any other files.
  4. To pass this assignment, just fill in the blanks in answer03.c. The
  5. comments in this file are there to guide you. You can (and should)
  6. create extra functions as needed. Please take care to follow the
  7. coding standards of the course. (For example, do not use any static
  8. variables.)
  9. Once you finish the solution, and it passes all of the testcases, and
  10. everything is *neat* and *tiddy* in your source file, and you compile
  11. without warnings, then please submit it to blackboard.
  12. ===============================
  13. == To Sumbit Your Assignment ==
  14. ===============================
  15. You must submit a zip file called "pa03.zip", with precisely two files
  16. in it: "answer03.c", and "my-log.text". You must submit only those
  17. two files, and they must be named precisely as described.
  18. =====================================================
  19. In PA03-PA05, you need to show evidence of using version control. You
  20. can use any version control system (such as CVS, SVN, RCS...). This
  21. course encourages you to use github.com because you can request free
  22. private repositories as a student. Please visit
  23. https://github.com/edu
  24. to get your free private repositories. You *MUST* use a private
  25. repository. If you use a public repository (visible by everyone in
  26. the world) and someone copies your solution, you will be considered
  27. cheating. You will receive F and your name will be reported to the
  28. Dean of Students.
  29. If you are new to version control, please understand what should be in
  30. version control and what should not.
  31. Version control manages different versions of the same text files, for
  32. example, source code and Makefile. Version control gives you
  33. line-by-line comparison of different versions. You should put the
  34. text files you write into version control.
  35. Version control does not work well with binary files because
  36. line-by-line comparison makes no sense. If you put binary files into
  37. version control, the file is still saved but comparison is impossible.
  38. As a result, putting images into version control would be
  39. questionable.
  40. You should *not* put computer-generated files into version
  41. control. Examples are object files and executable. If you write
  42. python programs, .pyc files are computer-generated. These files change
  43. every time you modify the source code. The source code should be
  44. managed by version control and the object files can be regenerated.
  45. Your Makefile should have "clean" to remove object and executable
  46. files. Do "make clean" before you commit.
  47. The evidence is the log (or history) of your commit. You should
  48. commit often (at least once a day). You can commit once an hour, or
  49. even once every 10 minutes. Each commit takes a snapshot of your
  50. programs. If you commit, you can easily recover from mistakes. If
  51. you do not commit, you will not have any history of the progress. To
  52. meet the requirement of PA03-PA05, you must commit *at least three*
  53. times and each of a meaningful message. In the rare cases when a
  54. student is suspected cheating, the student's commit log may be
  55. considered as an evidence for defense.
  56. For your reference, this is the commit log of the programming
  57. assignments.
  58. commit 5a80c29a3679fca017005c3ef0d1ea9e00f5423f
  59. Author: amichaux <amichaux@blakes-7.(none)>
  60. Date: Sat Aug 24 16:00:01 2013 -0400
  61. PA03 is ready to go
  62. commit d7ae597dcf8da12956fe9aab5c48252d214b3b5d
  63. Merge: a8790ab fcd3811
  64. Author: amichaux <amichaux@blakes-7.(none)>
  65. Date: Sat Aug 24 12:15:34 2013 -0400
  66. Fixed the Makefile for PA02
  67. Merge branch 'master' of https://github.com/yunghsianglu/ECE264Assignments
  68. commit a8790abba502ae254c8aefd9727c769f395e9d52
  69. Author: amichaux <amichaux@blakes-7.(none)>
  70. Date: Sat Aug 24 12:15:31 2013 -0400
  71. Fixed the Makefile for PA02
  72. commit fcd381110dccb96da660d3d70fa6f47425bf50b5
  73. Author: Aaron Michaux <amichaux@ecelinux12.ecn.purdue.edu>
  74. Date: Fri Aug 23 15:36:39 2013 -0400
  75. Fixed dependency -- make will compile target before running tests
  76. commit f6765efe5359b31ba9a08662d1cade3f2ecfa780
  77. Author: yunghsianglu <yunglu@purdue.edu>
  78. Date: Fri Aug 23 10:04:30 2013 -0400
  79. explain the assignments are graded
  80. commit 823993f487bad3245bec8ef1948b1a42ab4c035d
  81. Author: yunghsianglu <yunglu@purdue.edu>
  82. Date: Fri Aug 23 09:49:16 2013 -0400
  83. some hints for students
  84. commit edc7875818342cfb6fac8ddf8043e30ad8df4977
  85. Merge: 65427a9 c4721e7
  86. Author: Aaron Michaux <amichaux@ecelinux12.ecn.purdue.edu>
  87. Date: Thu Aug 22 22:30:52 2013 -0400
  88. Merge branch 'master' of https://github.com/yunghsianglu/ECE264Assignments
  89. commit 65427a9dd516eda01ce488987c1276b85cb9d47c
  90. Author: Aaron Michaux <amichaux@ecelinux12.ecn.purdue.edu>
  91. Date: Thu Aug 22 22:30:43 2013 -0400
  92. testing now depends on the target
  93. commit c4721e7497abcdfdb33a35e0fef99067e5585569
  94. Author: yunghsianglu <yunglu@purdue.edu>
  95. Date: Thu Aug 22 18:34:58 2013 -0400
  96. build the program if necessary when testall
  97. commit edc3efb4c16da07d55fb4c92e5caf53977ca8f40
  98. Author: yunglu <yunglu@yunglu-Latitude-E6320.(none)>
  99. Date: Wed Aug 21 17:34:15 2013 -0400
  100. explain the states
  101. commit ea01fe5c15a09c1b542bbea38fc18bc24ecb9b33
  102. Author: yunghsianglu <yunglu@purdue.edu>
  103. Date: Sun Aug 18 15:13:59 2013 -0400