HaxeFlixel/flixel — pull request #829 by impaler (2014-01-28 09:31:28+00:00)
Title: Cosmetic changes to function keyword order

Hi guys I was talking with @Gama11 about the order of the keywords in Flixel that are different to majority of the libraries out there. Firstly as a user you want to know if it is private or public first, inline and static etc are not the kind of information a user needs to know in most cases.

Anyone object to this and want to keep to the old convention we have been following from the original Flixel here?

The following replacements were run and it looks like nothing is broken, more testing required just in case:

```
inline static private function
private inline static function

static private function
private static function

inline static public function
public static inline function

inline public function
public inline function

inline static public var
public inline static var

static public var
public static var

static public function
public static function
```

Since Haxe defaults functions to private we could also look at changing `private function` to just `function`. There was some problems compiling doing this automatically everywhere with the interface implementations etc.