gramanicu/cpreprocessor

A simple C Preprocessor, the first homework for the Operating Systems Course

Grama Nicolae

I am a Computer Science and Software Engineering Undergraduate, passionate about technology & programming. I am a fast learner, very ambitious, good at searching and finding solutions to different problems.

cpreprocessor's Issues

Nmake implementation

Port all the Makefile rules from make (linux) to nmake(windows)

Data Structures Implementation

Implement all the required data structures:

• pair
• list
• hashmap

Build them as libraries, which are there used by the main program.

Replace 0 pointers with NULL

For more clarity, nullptr pointers should be written as NULL (or nullptr macro), instead of 0.

Implement Unit Testing (using cmocka)

Import and try to use the cmoka unit testing framework. Implement unit tests for every function (or the most important ones)

Implement coding style translation

My personal coding style is the one used during development and in this repository, but the linux kernel coding style is the one that will be used in the "solution archive" (according to the problem statement)

Initialize all allocated memory

All the dynamic memory allocations should use calloc instead of malloc (to make sure there are no "uninitialized pointer" bugs)

Switch #includes from <> to ""

Because of problems with the windows compiler, remove the library.

Function return error codes

All functions (or the ones where it is possible) should return an int, their error code.

Implement preprocessing

Implement all the logic behind the preprocessor:

• simple defines
• recursive defines
• includes
• conditional defines
• multiline defines

Write the documentation (Readme)

Write the Readme.md documentation, using these guidelines:

• write the name and class
• homework name
• organization:
  • explain the code structure
  • some explanations about how the code works and why it was used
  • speed, how "elegant" the code is, possible improvements
  • corner cases that were not included in the problem statement and how they are handled
• implementation:
  • if all the problem statement's requirements were implemented
  • extra functionalities (if they are, and why they exist)
  • missing functionalities
  • difficulties
  • interesting stuff
• compilation and execution
• bibliography / sources

Parse arguments

Parse the command-line arguments received.

• -D<SYMBOL>[=<MAPPING>] - define the symbol SYMBOL and assign the value from MAPPING. If mapping is empty, the value will be equal to ""
• -I<DIR> - add a directory that will be used to search for the files specified with the #include directive
• -o<OUTFILE> - the file where to store the processed code
• <INFILE> - the source code file. If not specified, the code will be read from STDIN