Invoking splint across C source and header files in a large project is tedious, requiring UNIX find commands the like to identify the file paths to send to splint, and this tends to break in Windows environments where GNU find is difficult to setup. Could splint recursively scan directory paths for any C / header files on the user's behalf, for a more intuitive command line interface and a more portable workflow?