tree d716b61d2c02ef4d9fcd73539ab752b4a1f88cc9
parent a88906b423e57e74a5bbaf1e315a58770d51c628
author FRIGN <dev@frign.de> 1456443413 +0100
committer sin <sin@2f30.org> 1456480486 +0000

Add symbol to mark NUL handling in each tool (and where it is missing)

The assumption of NUL-terminated strings is actually quite a good one in
most cases. You don't have to worry about paths, because they may not
contain NUL.
Same applies to arguments passed to you. Unless you have to unescape,
there is no way for you to receive a NUL.

There are two important exceptions though, and it's important that we
address them, or else we get unexpected behaviour:

	1) All tools using unescape() have to be strict about delimlen.
	   Else they end up for instance unescaping
	   	'\\0abc'
	   to
	   	'\0abc',
	   which in C's string-vision is an empty string.

	2) All tools doing line wrenching and putting them out
	   again as lines again.
	   puts() will cut each line containing NULs off at the first
	   occurence.