NOTE : Certain restrictions have been placed on the syntax. The
----   /[ and /] should occur on unique lines that contain no
       other symbols. Also, the $ syntax for C++ variables is
       rather cumbersome, because it seems to be required for
       the type as well.

       Functions used to 'export' builtin relations can only use
       some basic types as parameters. User defined types arent
       allowed. It is important to note that the translator does
       absolutely NO type checking or even any attempts to check if
       the exported function is defined in the file. It is a purely
       syntactic filter.

       Also, passing values from C++ to CORAL now seems convenient
       to use. However, the reverse interface is still pretty
       low-level (requires calling functions like make_tuple,
       make_relation, and call_coral). When the facility to
       manipulate tuples in CORAL is added (Tarun's working on it)
       we should have complete functionality in both directions.

       I'm not sure yet if there are any restrictions on use of
       embedded CORAL code in C++ code that is to be incrementally
       loaded. The catch here is that the parser needs to be
       called in a nested fashion, and YACC isnt reentrant. We
       should take a look at Bison which is reentrant, though I
       havent got around to it yet. 

       Apart from this, we seem to have pretty much the ability
       to intermix C++ and CORAL in arbitrary fashions.