#97 OBV confusing input params imlementation

[Alexander Trufanov]

I've implemented some logic to automatically assign my data to suitable TA function parameters and found out that it works incorrectly with OBV.

It looks like OBV requires Close and Volume values as described in wiki. So single TA_Input_Price parameter is enough to pass both. But it was implemented in a different way. It declares 2 input parameters - 1st TA_Input_Real and 2nd TA_Input_Price (only volume is used from 2nd param) as could be seen here.

This is confused my algorithm and I tend to believe that it is a bug, Thus I was going to fix it in my fork, but there is a chance that such implementation made on purpose.

It would has more sense if TA-lib authors expected that OBV may be used with values other than Close. Like Open\Volume, or High\Volume.

Is it so? Can I fearless fix it to Close in my code or this more flexible implementation is a must for someone?