en:toolworks:docs:apparatus:naming-conventions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
en:toolworks:docs:apparatus:naming-conventions [2021/09/01 17:42] vladiusen:toolworks:docs:apparatus:naming-conventions [2022/04/30 19:11] vladius
Line 1: Line 1:
 ====== Naming Conventions ====== ====== Naming Conventions ======
  
-There are certain naming conventions used within the framework of which every user you should be aware of.+There are certain naming conventions used within the framework. You should be aware of them, since they actually 
 +denote a certain behavioral semantics.
  
-Those are featured both is C++ and BP workflows:+Those are usually featured across both C++ and BP workflows.
  
 **Get** – get some property value or an item directly. If the get is non-trivial (indirect with a searching involved), also asserts the result is actually available (non-null). **Get** – get some property value or an item directly. If the get is non-trivial (indirect with a searching involved), also asserts the result is actually available (non-null).
  • en/toolworks/docs/apparatus/naming-conventions.txt
  • Last modified: 2022/05/13 13:07
  • by vladius