I just installed arduinoFFT-1.6.1 and compiled one of the examples only to get dozends of warnings. Actuallay, the warnings were telling me that #warning is getting deprecated
warning: #warning ("This method is deprecated and may be removed on future revisions.") [-Wcpp]
#warning("This method is deprecated and may be removed on future revisions.")
While I might ignore that warnings they will disattract me from noticing "real" warnings. This warning about warnings should be removed.
if the message is produced by an example sketch which is bundled with exact that version of the library, than you should inform the author of the library to fix that.
The warning is not being produced as a result of the sample sketch, but is hard-coded into the library. Compiling with empty setup() and loop() will produce the same warnings.
It appears the author of the library has made major changes to the way the library works, and has put that warning in the library .cpp file for every function that has been rewritten. The warnings are somewhat cryptic, since there is no indication of exactly what has been deprecated from the warning itself, you have to look at the library code to see which functions are deprecated.
Might have been better if the author had split off the new version of the functions into a separate library, similar to how the u8g library development stopped and was continued as u8g2.
well, the example sketch still includes the library.
If the library owner decided to bother users with warnings even if a function or a constructor isn't used, then that's also an information for the library owner and that you could look for other options.
It seems these warnings went into the code with Version 1.4
I would inform the library owner.