Simple 'bouncing ball' example posted on the wiki

[Jesper Juhl]

Hi people

This is just a quick message to let you know that I've posted a simple example program on the wiki. It just bounces a ball randomly around in a window. I wrote it in response to a forum post and would have left it at that, but then it became relevant in another forum thread and I thought I might as well make a wiki entry out of it.

You can find it here: https://github.com/SFML/SFML/wiki/Source%3A-Bouncing-ball

I hope you find it useful.
Comments and criticism is of course welcome.

[eXpl0it3r]

Just out of curiosity why did you name the "file" bouncing.cc? Never seen anyone use *.cc as file extension...

[Jesper Juhl]

No special reason except it's one of the extensions that g++ and clang++ by default recognize as C++ - from "man g++":

       file.cc
       file.cp
       file.cxx
       file.cpp
       file.CPP
       file.c++
       file.C
           C++ source code which must be preprocessed.  Note that in .cxx, the
           last two letters must both be literally x.  Likewise, .C refers to
           a literal capital C.
 

For headers I usually use ".h" for C headers and ".hh" for C++ headers, but there are of course other options. Again, from "man g++":

       file.hh
       file.H
       file.hp
       file.hxx
       file.hpp
       file.HPP
       file.h++
       file.tcc
           C++ header file to be turned into a precompiled header.
 

and it's also just what I've always used.
It's also fairly common in my experience; I've had several employers where that was the extension used and if you google for C++ code you'll often run into it.

Just out of curiosity, what do you normally name your C++ files?

[eXpl0it3r]

I see, well I've never seen a project using *.cc

I use *.cpp and *.hpp. From my experience *.cpp is the most commonly used for C++ files and thus it makes only sense to name the headers the same way.

[FRex]

I see, well I've never seen a project using *.cc

Google style guide says to use .h and .cc, and that's what many(?) of their projects use.

[eXpl0it3r]

From what I remember, Google's style guide has a few questionable bits.

[FRex]

But now you know of a few (very successful) projects using .cc.

[Jesper Juhl]

I see, well I've never seen a project using *.cc

Google style guide says to use .h and .cc, and that's what many(?) of their projects use.

I wouldn't use '.h' for C++ headers. GCC and Clang both treat .h as either C, C++, Objective-C or Objective-C++ by default and that's too much ambiguity and heuristics for me - see my post above for extensions they explicitly treat as C++ (only).