Differences
This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
|
Next revision
Both sides next revision
|
user:zeman:interset:how-to-write-a-driver [2008/03/14 10:56]
zeman Enforcing permitted feature structures. |
user:zeman:interset:how-to-write-a-driver [2008/03/14 12:16]
zeman driver-test.pl made more consistent. |
| |
| <code>driver-test.pl ar::conll | <code>driver-test.pl ar::conll |
| driver-test.pl -a | |
| driver-test.pl bg::conll cs::pdt | driver-test.pl bg::conll cs::pdt |
| | driver-test.pl -a |
| driver-test.pl -A</code> | driver-test.pl -A</code> |
| |
| Running ''driver-test.pl'' without arguments will list the drivers available on the system. Running it with the ''-a'' option will test all the drivers. Two arguments test both drivers separately and then conversions from driver A to driver B and vice versa. The ''-A'' option tests all conversions between all pairs of drivers. | Running ''driver-test.pl'' without arguments will list the drivers available on the system. Two (or more) arguments test both drivers separately and then conversions from driver A to driver B and vice versa. Running it with the ''-a'' option will test all the drivers but no conversions. The ''-A'' option tests all drivers and all conversions between all pairs of drivers. |
| |
| Note that only drivers implementing the ''list()'' function can be tested. Most testing involves generating the list of all possible tags and testing the driver on each tag separately. | Note that only drivers implementing the ''list()'' function can be tested. Most testing involves generating the list of all possible tags and testing the driver on each tag separately. |
