Try STLlint

This page will allow you to try STLlint online, by typing C++ code into the text box below and clicking "Run STLlint!". You should then be redirected to a list of error messages produced by STLlint as it would look in a terminal (STLlint acts just like a command-line compiler). There are a few things to remember when writing your code:

• Your code must be complete. If your C++ compiler can't compile it, neither can STLlint, and you'll just get back a set of errors from the C++ front end.
• Stick with the STL! STLlint is intended to check STL constructs, and doesn't far well with C-like constructs (typecasting, unions, arrays). Although STLlint does attempt to accomodate these bits to some extent, the support is far from perfect.
• Not sure what to write? The descriptions of what STLlint checks are full of little sample programs that show off what STLlint can do.
• Think you found a bug? You're probably right! STLlint is a complicated static analysis engine, and although we continually test it there are bound to be bugs. "Bugs" for a static analysis come in two flavors: actual bugs, which cause the analyzer to crash or produce incorrect results, and false positives, which are extraneous error messages produced because the analyzer either lacks appropriate information to make the correct decision or, more likely, has lost some precision in an attempt to return some answer in a reasonable amount of time. Feel free to report any bugs you find, and we will try to fix them if possible.

STLlint is developed by Douglas Gregor, a PhD graduate student at Rensselaer Polytechnic Institute.. STLlint's CGI script is graciously hosted by Dr. Sibylle Schupp, formerly of RPI and now at Chalmers.