Conventions/code/naming: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
I tend to use the following naming conventions within my code | I tend to use the following naming conventions within my code. | ||
==Prefixes== | ==Prefixes== | ||
These are more or less in keeping with the Apps (original) variation of {{l/wp|Hungarian notation}}. | |||
===Variable Prefixes=== | ===Variable Prefixes=== | ||
* '''f''': floating-point number | * '''f''': floating-point number | ||
Line 35: | Line 36: | ||
These may be used in declarations or variable names, but are generally used only for classes and objects. For classes, the <code>c</code> prefix comes first; for objects, these replace the <code>o</code> prefix, and sometimes may be the entire name of the variable. | These may be used in declarations or variable names, but are generally used only for classes and objects. For classes, the <code>c</code> prefix comes first; for objects, these replace the <code>o</code> prefix, and sometimes may be the entire name of the variable. | ||
==Value Types== | ==Value Types== | ||
* '''actual''' means a [[htyp:PHP/referencing|reference]]-container object | |||
** I prefer this to "reference" where possible. It's shorter, less misleading (''all'' PHP variables are references), and correctly implies that the entity in question is the actual thing and not a copy. | |||
* '''cell''' means access to a value in a named location (e.g. an array element) | * '''cell''' means access to a value in a named location (e.g. an array element) | ||
* '''ref''' | * '''ref''' is another shorthand for "reference"; see "actual". | ||
* '''slug''' means a string which can unambiguously represent any expected value or state of a given item | * '''slug''' means a string which can unambiguously represent any expected value or state of a given item | ||
** needed for representing record IDs in URLs, where one possible state is "new" (no ID yet) | ** needed for representing record IDs in URLs, where one possible state is "new" (no ID yet) |
Revision as of 22:35, 26 November 2021
I tend to use the following naming conventions within my code.
Prefixes
These are more or less in keeping with the Apps (original) variation of Hungarian notation.
Variable Prefixes
- f: floating-point number
- k or K: a constant, i.e. anything whose value should not (or cannot) change once defined
- n: a count (int; use f for float)
- o: object
- or: a ref object (see Value Types)
- os: a status object (see Value Types)
- s: string
- sc: string that is the name of a class
- sq or sql: string that is formatted as SQL, or safe to be used within SQL
see also General Affixes
Declaration Prefixes
- c: class
- ca: abstract class (cannot be instantiated)
- cs: static class (not intended to be instantiable; all methods static)
- ch: a string that is always a single character
- f: [DEPRECATED; use namespaces instead]: a Ferreteria class/trait/interface
- if: interface
- t: trait
see also General Affixes
I wanted to use "c1" (cee-one) as a prefix for singleton classes (i.e. a class for which there should never be more than one object), but it looks too much like "cl" (cee-ell) or possibly a typo, so I dropped that idea.
General Affixes
In the prefix but not necessarily as the first characters:
- db: a database
- rc: a single-record class/object
- rs: a recordset class/object
- t: a table class/object
These may be used in declarations or variable names, but are generally used only for classes and objects. For classes, the c
prefix comes first; for objects, these replace the o
prefix, and sometimes may be the entire name of the variable.
Value Types
- actual means a reference-container object
- I prefer this to "reference" where possible. It's shorter, less misleading (all PHP variables are references), and correctly implies that the entity in question is the actual thing and not a copy.
- cell means access to a value in a named location (e.g. an array element)
- ref is another shorthand for "reference"; see "actual".
- slug means a string which can unambiguously represent any expected value or state of a given item
- needed for representing record IDs in URLs, where one possible state is "new" (no ID yet)
- status means a presence-info object
- preferably descended from cThingHolder
- unit means something that knows its own name and has awareness of its container-object/structure
- preferably a PortRow Unit object
- value means a read-only value, assumed to exist (throws error if not)
Namespace Aliases
When creating an alias for a namespace, I use a single capital letter as shorthand for parent-folders of the current namespace -- not for folders outside of it.
Example: In namespace ferret\data\bank
, I might use D
as an alias for ferret\data
(use ferret\data as D;
), but I would not use that alias in namespace ferret\globals
. I would, however, use F
as an alias for namespace ferret
in both of them.