Whenever the software author includes self-test(s), I'm always trying to use it to make sure, the software built right (especially, if I had to patch it to compile cleanly).
Unfortunately, the apps/test.cpp is not very usable for this purpose... The first 3 tests are extremely verbose, but they complete fairly quickly. But the fourth test never ends -- if there is a problem, it should say so and report failure. But, if it hangs, it can not be used to automatically verify the build...
cd /home/ports/net/udt/work/udt4/app && /usr/bin/env LD_LIBRARY_PATH=/home/ports/net/udt/work/udt4/src ./test | /usr/bin/grep Test
Start Test # 1
Test # 1 completed.
Start Test # 2
Test # 2 completed.
Start Test # 3
Test # 3 completed.
Start Test # 4
... hang ...
The test is flaky. I will try to fix it. However the testing is very basic. It should be enough for the C++ style changes like you just submitted, but it is not enough for protocol/algorithm change.
Thanks!