kent logo

CO538 Anonymous Questions and Answers Keyword Index

This page provides a keyword index to questions and answers. Clicking on a keyword will take you to a page containing all questions and answers for that keyword, grouped by year.

To submit a question, use the anonymous questions page. You may find the keyword index and/or top-level index useful for locating past questions and answers.

Keyword reference for files


Question 1 (2001):

Where can I find the demo_cycles.occ library as mentioned in the q2.occ file?

Answer 1:

Under the "setup information" link from the Co516 web page, there is the encouragement to:

    ... browse around the directories off /usr/local/work/co516 ...
    ... in particular, read all the README files ...

If you do that, you will find the directory /usr/local/work/co516/libsrc, which contains the source codes for everything on the course library supporting this unit. As the README file in that directory says, it contains the files demo_cycles.occ and demo_nets.occ and these contain, respectively, the legoland catalogue studied in the course (slides 5-3 through 5-6) and some sample networks built from that catalogue (slides 5-8 through 5-13).

Note: you can also access these files from a web browser:


or directly from Windows under \\raptor\files\courses\co516\. To make this easy, a link to these files ("occam course files") has been added to the course web page.

Note: to use any of the PROCs or FUNCTIONSs in the libsrc directory, you do not need to copy over any of the files. So long as your program source files contain the line:

   #USE "course.lib"

you can invoke them freely. For some exercises (e.g. question 4), you will need to make some modifications to some of these library PROCs - in which case, you will need to take your own copies and start editing.

Keywords: files

Referrers: Question 3 (2001)

Valid CSS!

Valid XHTML 1.0!

This work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.
Last modified Mon May 20 13:50:27 2013
This document is maintained by Fred Barnes, to whom any comments and corrections should be addressed.