AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Gmod starfall music e23/12/2024 Once a branch is released, features cannot be added to it.Before complaining about this not working/being broken read Issues&Solutions AND the comments!Ī simple yet powerful and elegant music player which allows you to play your favorite music with the press of a button.When Hotfixes and patches are required, they will be added to the branch for that release and tagged.The leading commit will be tagged upon release. Minor versions will belong in a branch specifically for that release.E.g function helloWorld() may become deprecated between 2.0.0 and 2.1.0 and will be removed in 3.0.0.Functions can be deprecated between minor versions and will then be removed in the next major release.2.x.x set will always be cross-compatible. Only changes in major version can break compatibility, backwards compatibility is guaranteed within the same major version.We are using Semantic Versioning in the format of -minor.Good: print( a and "Hello" or "Hi" ) Bad: a and print("Hello") or print("Hi") Short circuiting, a = b and c or d, is only permitted if used as a ternary operator.Do not use semicolons at the end of statements, unless required to separate single-line multi-statements.Use of one-liners/ single-line multi-statements is discouraged.local var = 5 + 3 and local var2 = -var + 3. Use spaces before any unary operator before and after any binary operator.Use spaces before the argument list of a function definition.The last value must not have a proceeding comma. Table literals must be delimited by commas which proceed their values.( See table literal multi-line example below. Use spaces between curly braces and their enclosing body, it is also acceptable to use a newline with appropriate indentation instead.Use spaces between square braces and their enclosing body.Use spaces after commas, as well as semicolons.print( "Hello" ) & function f ( args ) & f( args ). Use spaces between parentheses and their enclosing body.if conditions/loop headers, unless absolutely necessary. No parentheses around conditionals used for program logic.Function and variable names are supposed to be in camelCase, constructor functions, however, are supposed to be in CamelCase.Add comments when code functionality is not clear or when the purpose of the code is not obvious.Use reasonable documentation for internal API functions and libraries. Use LuaDoc-style comments on external user API functions and libraries.Use tabs for indentation, don't use spaces or other whitespace characters.This is an example of what NOT to do: "fixes and changes".E.g " Burst/PersonalQuota/DefaultQuota for SF Holograms", "Fix entities not getting wrapped by SF.WrapObject" & "Added ents_methods:getColor()".
0 Comments
Read More
Leave a Reply. |