A few things to do with entry

  1. Well, obviously, why not build a short dictionary and try entry out?

  2. You will probably have noticed that this version of entry expects two inputs whereas the procedure which we originally proposed assumed just one, the key-word. A one input form is obviously easier on the user, but it is also more sensible when only one dictionary is to be used, since the key-word is the only input which can be varied. Providing a better interface is easy enough to achieve by defining a new super-procedure. The super-procedure, which will need a different name (unless you rename entry as, say, entry2), should take just the key-word as input and should do no more than output whatever it receives from a call to entry (or entry2).

  3. You could also modify entry to turn it into a more general key-word based search tool (perhaps called get) which is able to deal with simpler database structures of the form [[key x][key y][key z]]. (E.g. [[hair blue][eyes brown][height 1.75] . . .]). Could you then rework the definition of entry so that it uses get?

    Back to main text.



Ron Brasington
Department of Linguistic Science
The University of Reading
Reading
UK

E-mail: ron.brasington@rdg.ac.uk