Naming conventions - functions

[Laurent]

consistent with every other libraries

I wouldn't say that. There's no consistency in the C++ world; sadly, nobody uses the std/boost naming conventions.

I wonder how many people will want to use this library and how many give up because of the convention.

I don't choose a library by the naming convention it uses. As long as it doesn't pollute my public API, I really don't care.

So is there any decision about the convention in the new version?

Yes, the decision is that nothing will change. Sorry if it wasn't clear enough in the rest of the topic

[Tyrreus]

Ok thanks for your clarification Anyway, this lib is a pice of great job!

Regards

[gsaurus]

sadly, nobody uses the std/boost naming conventions.

Maybe because it isn't that good, I guess it is kept only for compatibility and historical reasons. To me it's just an old convention reflecting the old hardcore programming style.

Anyway the current SFML convention is fine, it's clean and easy to read, independently if people are used to other conventions or not.
Personally, if SFML used std/boost naming convention I may haven't chosen it, because I find it unnatural and hard to read. When smaller libraries use a convention (or API in general) that I find hard to understand, I wrap it with classes from my own, but for big and generic libs like SFML, simplicity and readability does matter.

[deadalnix]

First I liked the uppercase a lot, but then I started learning Qt and I really loved the lowercase. Anyway, it's too much work to change it and it doesn't really affect anything than code-reading perfection.

Well, code writing involve 90% of code ready. So I think this is a much biggger issue than you may think.

[Mikademus]

Yes, the trend in the industry over the last decade has been a move to lower-case comelCase for methods (Class::myMethod()), upper-case CamelCase for free functions (MyFunction()), all-lowercase without underscores for namespaces, and abbreviations treated as normal words (RenderRttStuff(), Class::rtsAndRttAreAcronyms()).

This is actually tremendously positive for code readability.

The boost and STL code conventions are only used there, but that too can be argued to serve the purpose of showing what is "language" and what is userland calls.