Methods were registered with wrong names

MOAIBox2DFrictionJoint._getMaxForce() -> getMaxForce()
MOAIBox2DFrictionJoint._getMaxTorque() -> getMaxTorque()
MOAIBox2DFrictionJoint._setMaxForce() -> setMaxForce()
MOAIBox2DFrictionJoint._setMaxTorque() -> setMaxTorque()
Changed C++ method names to fit Lua registration

MOAICpSpace::_insertProp() -> _insertPrim()
MOAICpSpace::_removeProp() -> _removePrim()

Seems like Patrick at some point renamed MOAIPrim to MOAIProp and
accidentally also renamed these methods although they deal in
MOAICpPrim's rather than MOAIPrim's.
Fixed method documentations
Fixed parameter documentation
Merge pull request #874 from DanielSWolf/doclint-fixes

Doclint fixes
Fixed disabling of ios host modules
Merge pull request #877 from JDaance/ios-build-fixes

Fixed disabling of ios host modules
Merge pull request #1 from moai/master

1.5
Fix wrong path and missing HTTP Client in Windows scripts
build-ios.sh: A couple of minor tweaks and adjustments.

"set -e" causes the shell to silently exit without comment under
some circumstances, so add a trap that catches that and diagnoses
what failed. Also, the usual build path can get quite far before
reporting that the SIGN_IDENTITY value isn't usable; check for that
right away up front, and error out then, rather than running a
long build first. A couple of minor tweaks to the argument processing,
also.

The reason to change the $# loop is that if you didn't pay attention
to the usage description,
	build-ios.sh --disable-foo
produces a very strange error message from the Ruby command, because
we end up with Ruby trying to parse "--disable-foo" as a command-line
option. (I think a -- might fix this, but went for a more explicit
check on arguments anyway.)
Merge pull request #883 from seebs/seebs/ios-build-tweaks

build-ios.sh: A couple of minor tweaks and adjustments.
Merge pull request #882 from romainmoreau/windows-scripts

Fix wrong path and missing HTTP Client in Windows scripts
Drop inline qualifier

According to clang, you aren't allowed to use inline when replacing
operator new/new[]/etc.
lcrypto: use unsigned int for functions taking unsigned int *

Four functions declared a "size_t" named written, then passed its
address to functions expecting an "unsigned int *". It is permissible
for size_t and unsigned int to be of different sizes, so that's
unwise.
xmplparse: Handle warning from clang

clang doesn't like it if you switch on an enum without handling all
its possible values. Add a probably-harmless default case for
the unhandled value.
MOAIUntzSampleBuffer.cpp: Drop unused variable

The "u32 total" wasn't used.
tlsf.c: Don't do a dummy assignment.

If you want to indicate that a function doesn't do anything, a plain
return is better than a dummy assignment. The assignment is probably
an attempt to silence compiler warnings about unused variables; most
compilers recognize "(void) value" as a way to hint that, so we do
that now.
Suppress warnings

Fix what is almost certainly a bug in an unused function, comment
out an unused value.
Fix various warnings:

* Initializer using == instead of =
* clang wants some values put in the order they'll be used, or it
  gives warnings
* unused variables
* in some cases, use the unused variables instead of repeatedly
  re-computing them.

Still some left, but this helps some.
sfmt: only declare sse2_param_mask if using it

No need to declare it if we're not using the code that relies
on it.