'tests' check that the code is working, and fail if the results
aren't what was expected.
'demos' simply run the code and show what it can do. The don't provide
any immediate assurance that it is doing the right thing.
Separate these into "make tests" and "make demos"
Signed-off-by: NeilBrown <neil@brown.name>
./md2c indent_test.mdc
itest: itest.c
./md2c indent_test.mdc
itest: itest.c
- tests:: itest itest.code
+ demos:: itest itest.code
./itest itest.code
# indent: header
./itest itest.code
# indent: header
things which will likely grow as the languages grows.
###### File: oceani.mk
things which will likely grow as the languages grows.
###### File: oceani.mk
- @echo "===== TEST ====="
- ./oceani --section "test: hello" oceani.mdc 55 33
+ @echo "===== DEMO ====="
+ ./oceani --section "demo: hello" oceani.mdc 55 33
$(CC) $(CFLAGS) -o calc calc.o libparser.o libscanner.o libmdcode.o libnumber.o -licuuc -lgmp
calctest : calc
./calc parsergen.mdc
$(CC) $(CFLAGS) -o calc calc.o libparser.o libscanner.o libmdcode.o libnumber.o -licuuc -lgmp
calctest : calc
./calc parsergen.mdc