On 04/18/2012 01:25 PM, David C. Rankin wrote:
> It is complaining about 'r' being declared twice below. This looks more like a
> reassignment than a redeclaration to me. How do we properly fix it?. If all we
> care about here is 'r' having function scope, can't I just get rid of the
> 'Range* ' typecast following the else { ? Or do I have to change 'r' to 'not_r'
> following the else?
Getting rid of the second 'Range* ' was the trick. Verify and then push patch :)
--
David C. Rankin, J.D.,P.E.
Attachments: