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 revisionBoth sides next revision
en:toolworks:docs:apparatus:naming-conventions [2022/01/05 13:03] – Некоторые очень маленькие ошибки быстрой печати исправлены jisparen: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 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 in 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