IsFit or IsFIT

Former Member
Former Member

I'm building an app in c++ (gnu C++ on Linux).

Your documents show that IsFit can be used to verify that a file is a fit file so I thought that this would be a nice 'hello_world' to write.

It won't compile.

I had a look through fit_decode.hpp and fit_decode.cpp and found that IsFit is declared thus :-

FIT_BOOL IsFIT(std::istream &file);

FIT_BOOL Decode::IsFIT(std::istream &file)

I changed my code to call IsFIT and it duly compiled and worked.

I would expect that the casing is important and consistent across all the libraries so why is the documentation using IsFit but the released (auto generated) code using IsFIT ?

  • The SDK is not consistent with the naming of this method. It is not an auto-generated method, and you will see both IsFIT() and IsFit() used. The Java SDK likes to stand out from the crowd and uses IsFileFit(). I am guessing that Intellisense helps most people get it right before the compiler ever knows what happened.

    Changing this to be consistent across SDKs is not something we would do until there is another major update to the SDK, which at this time is not planned.