Difference between revisions of "Papyrus Naming Conventions"
Jump to navigation
Jump to search
imported>Qazaaq |
imported>ShadeMe (Add to Papyrus Language Reference) |
||
| Line 1: | Line 1: | ||
*Generally: | *Generally: | ||
* a --> function argument | * a --> function argument | ||
| Line 29: | Line 26: | ||
---- | ---- | ||
[[Category: Scripting]] | |||
[[Category: Papyrus]] | |||
[[Category: Papyrus_Language_Reference]] | |||
Revision as of 02:15, 22 October 2017
- Generally:
- a --> function argument
- k --> object
- b --> boolean
- i --> integer
- f --> float
- s --> string
- p --> pointer (carryover from internal code, inconsistency, should not be used)
- r --> reference (carryover from internal code, inconsistency, should not be used)
Example:
Function MyFunction(int myNum, akActionRef) ak = Function Argument Object.
SmkViper helped flesh out this list. There doesn't appear to be any conformity to conventions with regard to local and script variables.
However:
- Properties tend to be upper CamelCase.
- Script variables tend to be upper CamelCase.
- Local variables tend to be lower camelCase.
- ReferenceAlias properties always have the "Alias_" prefix.
source: http://afkmods.iguanadons.net/index.php?/topic/4417-papyrus-naming-conventions/ There might be more in Fallout 4, these are from Skyrim