https://github.com/vmasek/IFJ-14

Group project 'pascal like interpreter written in C' for IFJ 2014
https://github.com/vmasek/IFJ-14

Last synced: about 2 months ago
JSON representation

Group project 'pascal like interpreter written in C' for IFJ 2014

• Host: GitHub
• URL: https://github.com/vmasek/IFJ-14
• Owner: vmasek
• Created: 2015-09-02T13:24:50.000Z (almost 9 years ago)
• Default Branch: master
• Last Pushed: 2015-09-02T14:33:46.000Z (almost 9 years ago)
• Last Synced: 2024-03-18T17:41:18.167Z (3 months ago)
• Language: C
• Size: 605 KB
• Stars: 3
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Lists

• AwesomeInterpreter - IFJ-14

README

        
# README #

# Makefile usage: #

For testing your modules create source file containing main function.

If is your source file placed in project directory, testing program

should be compiled wihout problems.

Compile program by calling `make` in project directory.

# Debugging: #

For enable debugging macros compile program with `-DDebug` switch.

Or run `build` script that has debugging on.

When using makefile try using this command. It has useful aditional gcc switches and Debug enabled.

`make -B FLAGS='-DDEBUG -g -Wstrict-prototypes -Wstrict-overflow=5 -Wwrite-strings -Wunreachable-code -Winit-self -Werror-implicit-function-declaration' `

# Tests: #

####ADVICE:	

When using test make sure that your normal main(), not the one in tests.c is located in main.c file, not just under your current testing implementation.

Otherwise it cannot be filtred out and tests will yell.

Two types of testing were implemented. Direct and by Script.

####Running tests directly:

- `./test_ifj`		will run all of the implemented tests.

- `./test_ifj [args]`		will run all test mentonied in [args].

Example:

- `./test_ifj stack` 		will run test for stack

- `./test_ifj kmp stack` 	will run test for kmp and stack

- `valgrind ./test_ifj kmp stack` 	will run test for kmp and stack and check them with valgrind

####Using test script:

All tests are made automatic. 

Output of tests is coloured to easily spot the error.

Run `./test` in Bash

####Advanced testing:

Use script arguments to specify test:

- `mem`:		test memory allocation/deallocation (valgrind and advanced valgrind)

- `debug`:		tests will be runned with debugging macros turned on

- `delete`:		test will be forced to delete every log and temp file

- `log`:		test will be forced to STORE all log files

- `ok`:			test will always show returned err. code

- `modules`:	modules will be tested

- `project`:	project will be tested

Running project test located in directories/subdirectories:

- `ours`:		our all tests

- `scanner`:	our scanner tests

- `expr`:		our expr tests

- `syntax`:		our syntax tests

- `strins`:		our syntax tests

- `float`:		our float errors tests

- `strings`:	our strings tests

- `skal`:		tests made by "Skal"

Adding tests to script:

If you want to add new test that you just implemented:

	1.   Open script.

	2.   Add keyword to array.

	2.1. If needed, add keyword to array that will redirect test output to file.

	3.   Use.

# 1337 IFJ projectis #