SFML community forums
General => Feature requests => Topic started by: NeWsOfTzzz on August 20, 2008, 02:36:08 pm
-
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
-
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 ;)
-
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!
-
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.
-
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!
-
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 ?
-
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...
-
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.
-
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 :D
-
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:
-
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.
-
Besides, SFML isn't the only library that uses this naming convention.
-
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!
-
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" ...
-
The point is, there's no "standard convention."
False.
false.
-
Plz dont say anything when you don't know: C/C++ have standard conventions: ISO/IEC 14882:1998 && ISO/IEC 14882:2003.
-
No, they don't.
The only thing which can't be used is __xxx and _(UpperCase)xxx because this is reserved for implementation (17.4.3.1.2 iso C++).
-
They dont say it explicitily but they always name their function in lowercase and classe with one letter to uppercase (the first one).
Anyway i'm stoping this discussion right now :D on this: C++ have a standard convention. A "Standard non official" convention says that classe must start with an uppercase letter and variable/functions must start with lowercase to have a "distinction". BUT ANYWAY the lib have his own convention and that it.
-
This is going nowhere so I suggest the following procedure instead of debating:
-type "C++ naming convention" in google
-read first three or four answers
-type "http://www.parashift.com/c++-faq-lite/coding-standards.html" in you URL bar
-read the entire page
I believe it shows quite easily that there is no C++ standard even a non-official one.
-
I love the library but it needs to be forked because the admin is shallow minded and bull headed.
-
If you want to fork juste because of a naming convention, then you are probably narrow minded.
-
If you want to fork juste because of a naming convention, then you are probably narrow minded.
It's shallow-minded and bull-headed too.
-
Ok. I'll admit it. your turn.
-
I'd rather continue to ignore this silly thread, but now I feel compelled to say that I'm sure 99% of the people using SFML appreciate the work Laurent et al have been doing and aren't hung up on the naming convention.
-
You shouldn't care so much about naming conventions.
What matters is that the name gives you a hint about what something does or is.
Obsessing over a naming scheme just shows that you haven't been coding very long.
I don't understand how you can insult Laurent on his own forum about his own software.
// SFML - Simple and Fast Multimedia Library
// Copyright (C) 2007 Laurent Gomila (laurent.gom@gmail.com)
//
// This software is provided 'as-is', without any express or implied warranty.
I very much appreciate Laurent's hard work and have no problem with his naming scheme.
I've even adopted the "my" prefix in my own code (though I still maintain a lowercase first character in function names, etc).
-
Even C++ compilers are not standardized :D . Just look at the mess in boost source code. That's what you'll get when you try to make everyone happy.
And most IDE have code completion, who cares about upper or lowercase?
-
Epic drama?
-
I'd rather continue to ignore this silly thread, but now I feel compelled to say that I'm sure 99% of the people using SFML appreciate the work Laurent et al have been doing and aren't hung up on the naming convention.
Agree. Anyway, I got the impression that most of feature requests would only make less than 1% of SFML users satisfied... :roll: