en:toolworks:docs:apparatus:flagmark

Differences

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

Link to this comparison view

Next revision
Previous revision
en:toolworks:docs:apparatus:flagmark [2021/12/06 22:39] – created vladiusen:toolworks:docs:apparatus:flagmark [2021/12/06 22:50] (current) – [Matching] vladius
Line 1: Line 1:
-====== Flagmark ======+====== Flagmarks ======
  
-The //flagmark// is a lightweight per-Subject fixed set of flags. It is essentially a 32-bit integer internally that is most easily tested against at runtime.+//flagmark// is a lightweight per-Subject fixed set of flags. You could meet a different terminology in other engines like "tag components" or "flag components" for a similar functionaly. In Apparatus it is essentially a 32-bit integer that can be trivially tested at runtime
 + 
 +===== Matching ===== 
 + 
 +The flagmarks are always matched at runtime, during the iterating/operating process exactly. They are not cached or pre-matched in any way. This should not be a performance issue though, since the checks are just integer being binary op'd with two other integers and that's it.
  
  • en/toolworks/docs/apparatus/flagmark.1638819579.txt.gz
  • Last modified: 2021/12/06 22:39
  • by vladius