You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Push spec calls for a set of test vectors to ensure compliance:
Test suite scheme: A more-or-less standardized "test suite" scheme is intended to help ensure that a Push implementation behaves like other implementations. The scheme is to process three files (a configuration file, a file containing a list of literals for initializing the stacks, and a file containing a program) and to produce an output file that contains a list of literals which, if read back in to the interpreter (that is, if "executed" as a program), would re-create the stacks as they were at the end of the computation. The values in the output file are listed type by type, following the order in which types are declared in the configuration file. Each implementation should also provide some mechanism for comparing its output files with those of other implementations (for example by reading the files and comparing stack states, or by comparing the files in a way that disregards insignificant white space). For systems that use configuration code, rather than configuration files, this scheme would have to be altered somewhat.
I went poking around other implementations looking for such a test vector suite, independent of code, that we could re-use for PlushScript but didn't succeed in finding something suitable. Do you know how we can get one to test PushScript?
The text was updated successfully, but these errors were encountered:
The Push spec calls for a set of test vectors to ensure compliance:
I went poking around other implementations looking for such a test vector suite, independent of code, that we could re-use for PlushScript but didn't succeed in finding something suitable. Do you know how we can get one to test PushScript?
The text was updated successfully, but these errors were encountered: