Known issues with jFUF v. alpha0.1

• Exceptions:
  • Some methods shade exception from underlying methods that shouldn't been shielded.
  • edu.columbia.surge.Unifier.unify() method should throw an exception under incorrect unification.
• Unifier engines:
  • We don't have any native unifier engine available right now. We want to incorporate a JNI interface to cfuf, I'm looking for a new project student to work on that. A long term goal would a pure Java unifier.
  • The TCP/IP server in lisp has two versions. One that only accepts connections from the local host and one that accepts them from every host. This last version is very insecure. Use it at your own risk! Feel free to contribute an improved version (the best would be an IP secured version --only certain IPs can access it-- or password protected in an SSL tunnel)
  • The local client, invoking lisp by command line doesn't work. It will need to be changed for different OS, versions of lisp, etc. It's included just to help implement one at hand.
• We provide a gateway to access SURGE functionality. A FUF one is up to discussion.
• We still miss two interesting extensions:
  • java.text compatibility
  • FDs with holes, that is, externally modifiable named slots.
  • Documentation:
    • The documentation should be spell-checked. Sorry about it.
    • More examples of use are needed.