Giter Site home page Giter Site logo

michaelnoguera / 537-proj2 Goto Github PK

View Code? Open in Web Editor NEW
0.0 2.0 0.0 4.59 MB

"Shared Memory Producer/Consumer Program", CS 537 Programming Assignment 2 (Fall 2020).

License: MIT License

Makefile 6.52% C 78.36% Shell 8.43% C++ 6.69%
c multithreading thread-safety circular-buffer test-automation makefile

537-proj2's Introduction

CS 537 Programming Assignment 2 (Fall 2020)
Michael Noguera ([email protected]) and Julien de Castelnau ([email protected])
due 10/13/2020 at 5pm

== BUILDING ==

To build, run "make" at the root of this directory. If you specify the DEBUG environment
variable as "true" or use "make DEBUG=true", debug symbols will be included in the 
executable as well. You can also run the scan-build target to build with the Clang static
analyzer, and scan-view to view the generated output in a web browser.

Use "make clean" to get rid of object files and executables.

== USAGE ==

prodcomm takes input from standard input, so text can either be typed in and then terminated
with Ctrl-D (EOF), or it can be piped in from a file like so:

./prodcomm < test.txt

The output will be printed to standard output or it can be redirected like the input.

== PROJECT STRUCTURE ==

The functionality of prodcomm is divided into four logical modules, which serve the
 following tasks:

1. main: Initialize the three queues and call pthread_create for each worker.
2. workers: Code for Reader, Munch1, Munch2, and Writer processes, as well the helper 
            routines they require to operate (such as reader_readline)
3. queue: Queue backend and the functions that operate on queues 
          (Initialize, Enqueue, Dequeue, PrintStats).
4. stat: Statistics backend and interface, used by Queue for tracking 
         enqueue/dequeue count and time.

== TESTING FRAMEWORK ==

"make test" runs our test script which compares the output of prodcomm against a mock script
that performs the same text transformation, written in bash. Each text file in the tests 
will be tested against the expected output, and a summary of which tests passed and failed
will be printed to standard output. The stderr output from prodcomm containing statistics and
other warnings is also redirected to test.log.

537-proj2's People

Contributors

michaelnoguera avatar panther03 avatar

Watchers

 avatar  avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.