This version of Learn Prolog Now! embeds SWI SH , SWI-Prolog for SHaring. The current version rewrites the Learn Prolog Now! HTML on the fly, recognising source code and example queries. It is not yet good at recognising the relations between source code fragments and queries. Also Learn Prolog Now! needs some updating to be more compatible with SWI-Prolog. All sources are on GitHub:
LearnPrologNow LPN SWISH Proxy SWISH

12.5 Practical Session

In this practical session, we want to combine what we have learned about file handling with some topics we met in earlier chapters. The goal is to write a program for running a DCG grammar on a testsuite, so that the performance of the grammar can be checked.

What is a testsuite? It is a file that contains lots of possible inputs (and expected outputs) for some program. In this case, a testsuite will be a file that has lists representing grammatical and ungrammatical sentences, such as [the,woman,shoots,the,cow,under,the,shower] or [him,shoots,woman] . The test program should take this file, run the grammar on each of the sentences, and store the results in another file. We can then look at the output file to check whether the grammar answered everywhere the way it should have. When developing grammars, testsuites like this are extremely useful for making sure that any modifications we make to the grammar don’t have unwanted effects.

Step 1

Take the DCG that you built in the practical session of Chapter  8 and turn it into a module, exporting the predicate s/3 , that is, the predicate that lets you parse sentences and returns the parse tree as its first argument.

Step 2

In the practical session of Chapter  9 , you had to write a program for pretty printing parse trees onto the screen. Turn that into a module as well.

Step 3

Now modify the program so that it prints the tree not to the screen but to a given stream. That means that the predicate pptree should now be a two-place predicate taking the Prolog representation of a parse tree and a stream as arguments.

Step 4

Import both modules into a file and define a two-place predicate test which takes a list representing a sentence (such as [a,woman,shoots] ), parses it, and writes the result to the file specified by the second argument of test . Check that everything is working as it should.

Step 5

Finally, modify test/2 , so that it takes a filename instead of a sentence as its first argument, reads in the sentences given in the file one by one, parses them, and writes the sentence as well as the parsing result into the output file. For example, if your input file looked like this:

[the,cow,under,the,table,shoots].

[a,dead,woman,likes,he].

the output file should look something like this:

[the, cow, under, the, table, shoots]

   s(
      np(
         det(the)
         nbar(
            n(cow))
         pp(
            prep(under)
            np(
               det(the)
               nbar(
                  n(table)))))
      vp(
         v(shoots)))


[a, dead, woman, likes, he]

no

Step 6

Now (if you are in for some real Prolog hacking) try to write a module that reads in sentences terminated by a full stop or a line break from a file, so that you can give your testsuite as

the cow under the table shoots .

a dead woman likes he .

instead of

[the,cow,under,the,table,shoots].

[a,dead,woman,likes,he].

Step 7

Make the testsuite environment more sophisticated, by adding information to the input file about the expected output (in this case, whether the sentences has a parse or not). Then modify the program so that it checks whether the expected output matches the obtained output.

eXTReMe Tracker
© 2006-2012 Patrick Blackburn, Johan Bos, Kristina Striegnitz