Why is it, that you advice to use #include "SDL.h"
instead of #include <SDL2/SDL.h>
? (Of course the used include path has to be updated)
There are many advantages of the latter over the former:
- It is obvious that SDL2 is used
- Avoids conflicts with an also installed SDL1 especially when both may be used in one project (I do have a case where this is the way)
- Does not require additional includes for default installs (SDL2/SDL.h is in /usr/include which is in the default path)
- Avoids conflicts with user code (A user might have a wrapper/util/… that he would want to name SDL.h too), the (unnecessary relative include path breaks this. Even
#include <SDL.h>
would be better)
So why?