Ditz issue update
Ditz issue update
Rename buffer variant API calls for consistency

All other API calls use "dynamic_buffer" and "fixed_buffer", so rename
duk_is_{fixed,dynamic}() to duk_is_{fixed,dynamic}_buffer().
Update API docs for buffer API call rename
API testcase fixes for buffer API rename
Release note: buffer API call rename
Merge branch 'api-buffer-consistency'

Rename duk_is_fixed() to duk_is_fixed_buffer() and duk_is_dynamic() to
duk_is_dynamic_buffer() for consistency with other API calls.
use duk_idx_t for nargs in function list

Trivial change, but match the typing for other 'nargs' arguments; duk_idx_t
is technically the correct type because nargs refers to the number of value
stack arguments expected by the function.
Merge branch 'api-nargs-consistency'

Change 'nargs' typing in function list from duk_int_t to duk_idx_t, for
consistency with other API occurrences of 'nargs'.
Ditz issue update
Ditz issue update
Capitalize Duktape internal strings (\xFFValue)
Fix testcases for capitalized internal keys
Source comment fixes for int key capitalization
Update guide on internal property naming
Update internal doc on internal property naming
Improve internal string guide section
Release note: internal string naming
Merge branch 'capitalize-duktape-int-prop'

Change Duktape internal keys to begin with an uppercase character, e.g.
\xFFValue.  This makes the internal key naming convention easier for user
code: if the user key begins with a lowercase character (which is the
usual Ecmascript convention), the user internal key will simply be e.g.
\xFFfoo.

Double \xFF prefix can still be used by user code when the bytes that
follow are unknown, e.g. they are from an external source.

Also rewrite parts of Guide internal properties section for perhaps
more clarity.
Release note: typofix