The Mathworks, Inc.

Bryan T White

Jason D Breslau

Joseph F Hicklin

John Norris Little

Nausheen B Moulana

Vadim Teverovsky

David A Foti

Halldor Narfi Stefansson

Joseph R Bienkowski

Jianzhong Xue

Christian R Weigandt

Koh M Shimizu

Systems and methods for function argument checking are disclosed. The systems and methods can use declarations and validation instructions based on the declarations. Validation instructions for a function can be generated automatically from a declaration for the function. The validation instructions can be executed in response to invocation of the function. The validation instructions can include instructions for determining whether an input satisfies a condition on a corresponding argument of the function, instructions for identifying a position of the input, and instructions for providing, in response to determining that the input does not satisfy the condition, an indication of the nonsatisfaction of the condition and the position. The condition can specify a datatype or size for the argument or one or more validation functions for checking the argument.

Systems and methods for function argument checking

A system may obtain an executable code segment of program code. The executable code segment may be associated with an emitter, and the program code, when executed, may be associated with a plurality of execution states. Each execution state, of the plurality of execution states, may correspond to a state of execution at a point in the execution of the program code that causes an event, of the plurality of events. The system may execute the executable code segment. The system may receive, from the emitter and based on executing the executable code segment, a program state corresponding to the particular execution state. The emitter may emit the information based on a particular event caused by executing the executable code segment. The system may collect the program state and information describing the particular event.

Collecting structured program code output

In an illustrative embodiment, an apparatus, computer-readable medium, or method may be configured to avoid command mistakes and suggest corrections. Known commands may be accessed which may include at least one expected identifier, alternative identifier, and/or identifier pattern. The frequencies of occurrence of the known commands may be calculated. A command with entered identifiers may be received and at least one possible mistake in the entered identifiers may be detected. A first numerical score for the known commands may be calculated using a string matching algorithm, a keystroke penalty matrix, and/or the detected at least one possible mistake. A second numerical score may be calculated using the frequencies of occurrence of the known commands and the first numerical score. Expected identifiers may be selected using the first and second numerical scores. A user-selectable command may be created using the expected known commands and displayed.

Mistake avoidance and correction suggestions

Growing community of inventors

Holliston, MA, United States of America

Bryan T White