This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| en:toolworks:docs:apparatus:flagmark [2021/12/06 22:43] – vladius | en:toolworks:docs:apparatus:flagmark [2021/12/06 22:50] (current) – [Matching] vladius |
|---|
| ====== Flagmark ====== | ====== Flagmarks ====== |
| |
| A //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. | A //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 ===== | ===== Matching ===== |
| |
| The flagmarks are always matched at runtime, during the iterating process exactly. They are not cached or pre-matched in any way. | 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. |
| |