Currently, the Pattern Search return codes are handled via a character string (NCODE). The character strings applied in patsh.js appear in the user interface without benefit of any intermediate layer.
Presumably, it would be better software engineering for patch.js to return an integer (or perhaps a bit field?) that is then interpreted by higher layers of software into the character string that appears in the user interface. Among other things, this approach would aid localization (internationalization).
Currently, the Pattern Search return codes are handled via a character string (NCODE). The character strings applied in patsh.js appear in the user interface without benefit of any intermediate layer.
Presumably, it would be better software engineering for patch.js to return an integer (or perhaps a bit field?) that is then interpreted by higher layers of software into the character string that appears in the user interface. Among other things, this approach would aid localization (internationalization).