Hi Laurent,
I've just checked out the new SFML snapshot with the new naming, and I just thought about posting about it when I saw this thread.
I've experienced other renamings in the past (in connection with SFML) so this didn't catch me off guard, and I don't want to tell you which convention to use, but you should definitely decide it now.
Personally I prefer the lower_case writing of everything, I don't even use Class names, I only like to use UPPER CASE for #define stuff, except header guards. For example:
#ifndef header_h
#define header_h
#define ZERO 0
const int global_variable = 1;
namespace a_name_space
{
class a_class_name
{
private:
int this_is_a_long_variable;
protected:
public:
a_class_name() : this_is_a_long_variable( 1 )
{
do_some_stuff();
}
};
}
#endifand since I use KDevelop I can use its handy reformat source functionality, which lets me set up a personalized code look.
Also it has a nice auto-completion feature, so no matter what convention you use I'm perfectly comfortable with it
Another thing is function names, those should be made permanent as well.
For example the recent ShowCursor vs. setMouseCursorVisible
and sf::Timer::Reset vs Restart vs restart
I'm really looking forward to the stable SFML 2.0
