I’ve gotten a link to the Big List of Nasty Strings several times in the last couple of days, so it must be going around the social media again. I’ve already used it for a number of years as a second set of strings to test after my first line of strings (including Hamlet) if I have time.
But you know what the BLNS lacks? Code comment markers and other code keywords. Oh, yeah. I like to use these:
""" Python Comment
comment that spans multiple lines"""
''' Python Comment
comment that spans multiple lines'''
""" Python Multiline comment end
''' Python Multiline comment end
/* Comment */
*/ Comment ended
?> end PHP Script
REM batch and Oracle comment
-- SQL Line comment
GO //start SQL Script
/// C# XML Tag Comments
' Visual Basic comments
<!--- Cold Fusion Comments
<% ASP Comment <% Response.End %>
Try those bad Oscars out in your edit boxes. Keep in mind, they might well go into the database without a problem, but as with any other string test, half of the test (and quite often much of the fun) comes when your Web or other application is called upon to display these values again.
For example, WordPress itself cannot handle HTML comments and the end PHP script line above; when I first reviewed this post, the complete text of the post did not display and much of the blog itself did not display (as PHP after the end PHP line did not work).