1
General discussions / Re: Deprecated functions
« on: January 14, 2016, 04:20:37 pm »
As an industry practice, marking a method or variable as depricated is basically just saying "this is no longer the prefered way of doing this and could go away at any point!"
Your issues with the warning are easily countered, either via the library as Exploiter( sorry... too lazy to do it right..
) said, or can be handled on your end with ease. Having LESS information available to the developer is almost always the wrong choice. Now, if fields are marked as depricated that aren't, that's a different issue.
Now, to actually be useful, since you are using Visual Studio, you should be aware of the ability to disable warnings via the #pragma warning command ( https://msdn.microsoft.com/en-us/library/441722ys.aspx ). This should work on other compilers as well, but #pragma cross platform implementation is spotty at best, so I'm not saying that with confidence. You can also suppress warnings via the project settings.
Your issues with the warning are easily countered, either via the library as Exploiter( sorry... too lazy to do it right..
![Wink ;)](https://www.sfml-dev.org/forums/Smileys/default/wink.gif)
Now, to actually be useful, since you are using Visual Studio, you should be aware of the ability to disable warnings via the #pragma warning command ( https://msdn.microsoft.com/en-us/library/441722ys.aspx ). This should work on other compilers as well, but #pragma cross platform implementation is spotty at best, so I'm not saying that with confidence. You can also suppress warnings via the project settings.