C++ (And others too) aliases for functions

[NeWsOfTzzz]

The standard is to write methods with a lower-case letter, so could you make aliases for functions to have them as lower-case version too?

So for example

sf::String::GetText you make an alias sf::String::getText in the c++ version. This won't hurt anybody but will surely help your libraries in spreading!

PS: You need any help in coding? Your library is exactly what I always wanted :p

[Laurent]

The standard is to write methods with a lower-case letter, so could you make aliases for functions to have them as lower-case version too?

No
And please, don't start a troll about naming conventions, it already happened a few weeks ago and it brought nothing good.

PS: You need any help in coding?

I always need help to port SFML to new languages or systems

[NeWsOfTzzz]

The standard is to write methods with a lower-case letter, so could you make aliases for functions to have them as lower-case version too?

No
Could I make them and you implement them?

PS: You need any help in coding?

I always need help to port SFML to new languages or systems
I don't need anything but Windows/Linux and C++ so it wouldn't be in my interest!

[Laurent]

Hey, you're too fast

Could I make them and you implement them?

No.

I don't need anything but Windows/Linux and C++ so it wouldn't be in my interest!

Okay, no problem.

[NeWsOfTzzz]

Could I make them and you implement them?

No.

And why exactly? It'd be only an alias and people could choose if they want to use the uppercase or lowercase version and those aliases don't add any extra space in the executable, because the compiler handles them as the same function!

[Laurent]

Have you ever seen a library doing so, just to implement every possible naming convention and make everyone happy ?

Have you thought about the horrible mess it would produce, in the code, in the documentation and in the beginners' minds ?

[Daazku]

I hate the fact that the sfml use an uppcase letter in begin of a function  but we it's Laurent choice... But we can't change the library itself just because of that...

[quasius]

I couldn't care less and I don't understand why this topic keeps coming up.  Every library has a unique naming convention.  A logical consistency throughout that naming convention is far more important than conforming to every other pre-existing naming convention.  This is fortunate since the latter is impossible.

[Nexus]

The current SFML naming convention pleases me. In my own code, I use exactly the same system. I hope you'll keep it forever, Laurent

BTW: Those who want standard naming convention shall write a header with hundreds of #defines

[Daazku]

Personally i hate it because that not how i learned to name my function/variable and that not like the "official" convention but what can i do... nothing because its too long to change the name of all function, it's useless because all the current code builded with the current version use the current convention and if we change it some people will say: I don't like the convension! Plz change it!  :lol:

[quasius]

The point is, there's no "standard convention."  You could get several different answers from different professional coders.  It's not like Laurent decided to make up his own standard because he's such a maverick and he wanted to confuse his users.

[Avency]

Besides, SFML isn't the only library that uses this naming convention.

[Daazku]

The point is, there's no "standard convention."

False. But ANYWAY i don't care. Like i said it before: WE need to follow the sfml convention!

[pamaury]

How could you say there is a standard convention ? This is absolutely false, just look at a few libraries and you will see it. Even in the industry, there isn't one.
Furthemore, it's only a matter of style, you can't say "this one is standard" just because the first lettre is lowercase instead of uppercase, this is stupid!

A believe a more intelligent proposition would be to follow the standard of each language(I mean the one use the standard library), for example C++ uses "foo_bar", C# uses "FooBar", Java uses "fooBar" ...

[heishe]

The point is, there's no "standard convention."

False.

false.