Add future for octal, binary, and hexadecimal command line arguments.

I discovered that sending in numbers beginning with 0x, 0b, or 0o via the
command line will lead to an error while attempting to convert the string value
received to an int.  I hope to have time to resolve this (if it is quick).
Merge pull request #629 from lydia-duncan/intConfigFuture

Add future for octal, binary, and hexadecimal command line arguments. [reviewed by daviditen]

I discovered that sending in numbers beginning with 0x, 0b, or 0o via the
command line will lead to an error while attempting to convert the string value
received to an int.  This is due to a lack of support for bin/oct/hex string -> int
casts.  Add a future for this case so that we don't forget about it.