Versioning of files / Supported SDL2 version
Free-Pascal-meets-SDL-Website opened this issue · 1 comments
This issue is based on a discussion started in another issue #19.
Author: @suve
@Free-Pascal-meets-SDL-Website: I think we should formally define what "SDL version" means in our headers. So far, we've been (informally) going by "pick the newest function, if it was introduced in X.Y.Z, we put X.Y.Z as our version". This bug suggests that we should go with "what's the version of the library that we're 100% up-to-date with". Some parts can be newer than the X.Y.Z we're declaring, but no parts should be older.
Author: @Free-Pascal-meets-SDL-Website
@suve
I like the idea. The realization is tough though. We would need to track the version of every file individually as nobody is updating all the file at once, right? - What way do you propose?Just a comment at the first line?
Check the first line of sdljoystick.inc . What do you think of this simple solution for the time being? When all files reached a certain minimum version, we can say we support this particular version.
In the README.MD todo list we could also list all files which should be updated to a certain version.
As having worked on some files now, I wonder if a better solution will be just to add the version next to each inc-file in sdl2.pas as this makes it easily visible which version a part (inc-file) has. I started with this and I'm curious of this works out better.