Comment 5 for bug 1209594

Hi Renjith,

My only concern is regarding the possibility of different class names when we compare against QuantLib/C++. As we have many test cases, we would potentially causing many differences. I explain the reason below:

At certain point I plan to have a tool which is intended to compare our class hierarchy, method names and field names against QuantLib/C++. The process consists of generating XML documentation of JQuantLib and QuantLib using Doxygen. A tool in Python will be responsible for comparing both XML files, hiding differences we know can be hidden and telling us other differences we are not expecting to see.

Test cases can be moved to other files... I dont think there's any thourble... but it would probably imply on different class names when we compare against QuantLib/c++ in future, which would generate dozens of warnings.

I havent stopped by to analyze the problem so, maybe it's possible to improve the way it is without generating differences.

Please let me know what you think about it and let me know about your plans to improve it.

Note: things can be improved! there's no need to strictly follow exactly everything which was done in QuantLib/C++. On the other hand, we should do our best to keep our API as close as possible, whenever it is possible and convenient.