Use markit solution for source code

[BradleyA]

# >>>   In the future, Use markit solution for source code and create a wrapper during compile/build time ?
# >>>       This will change the extension case statement objective: move from comments to variables in compiled code
# >>>       move from comments in source code to variables in compiled code
# >>>       very different vision
# >>>     Use markit in the source code & insert; var BUILD_VERSION="${FILE_RELEASE}.`git rev-list HEAD | wc -l`"
# >>>      Or use markit; to create CHAR variable found in compiled code ?
# >>>           opening comment x.c 'var VERSION="' and ending comment '"'
# >>>           opening comment x.c 'char VERSION[] = "$Version: ' ${FILE_NAME}    ${FILE_RELEASE}.`git rev-list HEAD | wc -l`     ${TIME_STAMP} ${USER} `hostname -f` `git describe` and ending comment '$";'
# >>>                           x.o $Version: XXXX XXXX XXXX XXXX '$'
# >>>           opening comment x.c 'char VERSION_MESSAGE[] = "$Version_message: ' ${FILE_MESSAGE} ` and ending comment '$";'
# >>>                           x.o $Version_message: XXXX '$'