Naming conventions: Difference between revisions
m
→{{header|Raku}}: Fix up Perl 6 -> Raku, other typos
Thundergnat (talk | contribs) (Rename Perl 6 -> Raku, alphabetize, minor clean-up) |
Thundergnat (talk | contribs) m (→{{header|Raku}}: Fix up Perl 6 -> Raku, other typos) |
||
Line 1,058:
=={{header|Raku}}==
(formerly Perl 6)
Built-in object types start with an uppercase letter. This includes immutable types (e.g. Int, Num, Complex, Rat, Str, Bit, Regex, Set, Block, Iterator), as well as mutable (container) types, such as Scalar, Array, Hash, Buf, Routine, Module, and non-instantiable Roles such as Callable and Integral. The names may extend to CamelCase for compound words: IntStr, CaptureCursor, BagHash, SoftRoutine.
Line 1,064 ⟶ 1,065:
Non-object (native) types are lowercase: int, num, complex, rat, buf, bit.
Nearly all built-in subroutines, functions, methods and pragmas included in
All upper case names are semi-reserved. You are free to use them, but are warned that you may encounter future collisions with internal usage. Upper case names are used for pseudo-packages: MY, OUR, CORE, GLOBAL, etc., for relative scope identifiers: CALLER, OUTER, SETTING, PARENT, etc. and other things.
Variables in
In user space, there are very few restrictions on how things are named.
That being said, there are some community conventions which are encouraged, though not enforced.
=={{header|REXX}}==
|