Issue #109

Fixes issue #109 where nested parentheses within the parameter signature additional traits caused a failure to correctly recognise the signature as valid due to not matching the ParameterAbbrevDefinitionRegex.
I have removed the regex in favour of manually parsing the parameter signature so as to make the code clearer and more maintainable than what the regex would have had to become in order to match nested brackets within the additional traits as well as possible additional brackets in the signature description.
well, that's a call to be made on how much of an issue #109 actually is.
Can it wait a small while longer for the signatureparser or does it need to
be fixed right now.
If it was your original intent to do a disposable fix we may as well
proceed with that as its done and move to signatureparser asap.

With regards to magic numbers their positions would have been checked by
the initial call to IsValidParameterSignature but I can remove them by this
evening as well as change the PARAMETER_IDENTIFIER to provide the fix for
#107


On 15 July 2014 09:25, Z <notifications@github.com> wrote:

> In src/ParameterDefinitonParser.h:
>
> > -                parameter.name = captureGroups[1];
> > -                TrimString(parameter.name);
> > -
> > -                // Default value
> > -                if (!captureGroups[3].empty())
> > -                    parameter.defaultValue = captureGroups[3];
> > -
> > -                // Additional Attributes
> > -                if (!captureGroups[5].empty())
> > -                    ProcessSignatureAdditionalTraits(section, cur, captureGroups[5], sourceData, result, parameter);
> > -
> > -                // Description
> > -                if (!captureGroups[7].empty())
> > -                    parameter.description = captureGroups[7];
> > +
> > +            if (IsValidParameterSignature(signature)) {
>
> Well the signature parser is still far from getting into the master – but
> I really need it for some other tasks. So we can either:
>
>    1. Do this PR as a quick & dirty (but stable and solid!) fix (this is
>    what I had in mind)
>    2. Or bring the Signature parser to master sooner than I have thought?
>
> What do you think?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apiaryio/snowcrash/pull/146/files#r14922033>.
>