use checkType() in checkArgs() and checkReturnValue(). [DONE] Make IndependentTypesSpecification convert character vectors into InheritsTypeTest [DONE] If the last line has a return(.....), don't rewrite it twice. [DONE] Have to deal with validation of the return value Should know what the signature was for the actual call. This should be done in the C code. Currently, we have to explicitly call return() or checkReturnValue(). This is done by rewriting the code to replace calls to return, etc. with the relevant call. [PARTLY] Pretty printing for functions with type info. [NOTE] The order in which checkArgs() processes the signatures for a SimultaneousTypeSpecification is important when determining the matching signature that is passed to checkReturnValue. The error should come from the function ideally, not checkArgs or checkReturnValue. Too difficult to arrange in the prototype implementation with checkReturnValue(), etc. Wait until we do this in C.
[DONE] Make IndependentTypesSpecification convert character vectors into InheritsTypeTest
[DONE] If the last line has a return(.....), don't rewrite it twice.
[DONE] Have to deal with validation of the return value Should know what the signature was for the actual call. This should be done in the C code. Currently, we have to explicitly call return() or checkReturnValue(). This is done by rewriting the code to replace calls to return, etc. with the relevant call. [PARTLY] Pretty printing for functions with type info. [NOTE] The order in which checkArgs() processes the signatures for a SimultaneousTypeSpecification is important when determining the matching signature that is passed to checkReturnValue. The error should come from the function ideally, not checkArgs or checkReturnValue. Too difficult to arrange in the prototype implementation with checkReturnValue(), etc. Wait until we do this in C.: Should know what the signature was for the actual call. This should be done in the C code.
Currently, we have to explicitly call return() or checkReturnValue(). This is done by rewriting the code to replace calls to return, etc. with the relevant call.
[PARTLY] Pretty printing for functions with type info. [NOTE] The order in which checkArgs() processes the signatures for a SimultaneousTypeSpecification is important when determining the matching signature that is passed to checkReturnValue. The error should come from the function ideally, not checkArgs or checkReturnValue. Too difficult to arrange in the prototype implementation with checkReturnValue(), etc. Wait until we do this in C.
[NOTE] The order in which checkArgs() processes the signatures for a SimultaneousTypeSpecification is important when determining the matching signature that is passed to checkReturnValue. The error should come from the function ideally, not checkArgs or checkReturnValue. Too difficult to arrange in the prototype implementation with checkReturnValue(), etc. Wait until we do this in C.
The error should come from the function ideally, not checkArgs or checkReturnValue. Too difficult to arrange in the prototype implementation with checkReturnValue(), etc. Wait until we do this in C.: Too difficult to arrange in the prototype implementation with checkReturnValue(), etc. Wait until we do this in C.

Duncan Temple Lang <duncan@wald.ucdavis.edu>

Last modified: Wed Sep 28 06:56:38 PDT 2005