Ditz issue update
Code policy tool improvements

- Detect plain identifiers (e.g. 'fpclassify')
- Strip comments and literals for some checks
- Strip expect strings for API testcase checks
Avoid plain function names in math code
Avoid plain printf in debug code
Avoid 'exp' var name, shadows exp() from math.h
Avoid plain fprintf() in API macro
Avoid plain stream names, bug fix

duk_dump_context_stderr() would incorrectly dump to stdout.
Add _func suffix to struct duk_memory_function

Without the suffixes the struct used "free", "alloc", and "realloc".  These
shadow names from the standard library.  Usually this is not an issue, but
if the standard names are #defines, compile can fail.
Rename memory function members in API doc
API test case fix for memory function rename
Release note: memory function rename, etc
Merge branch 'code-policy-plain-fp'

Detect accidentally unwrapped math functions etc in code policy check.  This
would have caught the missing fpclassify() wrapping which broke the build on
some platforms.

This merge also fixes various offenders, and fixes a few small bugs.
Ditz issue update
Ditz issue update
Markup trivia for feature options
First draft of sandboxing documentation
Draft Guide section for sandboxing, refs RST
Merge branch 'sandbox-internal-doc'

Add first draft of sandboxing suggestions.  Sandboxing is not yet fully
thought out so these suggestions are not complete.  Duktape 1.0 does not
yet have bytecode executor timeout functionality, so there is no way to
implement protection against CPU hogging.  Internal property access and
buffer value access are in conflict and may need a better solution in a
later version.
Ditz issue update