2018-02-20 09:48:44 +00:00
|
|
|
---
|
|
|
|
|
layout: pattern
|
|
|
|
|
title: Dirty Flag
|
|
|
|
|
folder: dirty-flag
|
|
|
|
|
permalink: /patterns/dirty-flag/
|
2019-12-13 21:09:28 +02:00
|
|
|
categories: Behavioral
|
2018-02-20 09:48:44 +00:00
|
|
|
tags:
|
2019-12-13 21:09:28 +02:00
|
|
|
- Game programming
|
2018-02-20 09:48:44 +00:00
|
|
|
- Performance
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## Intent
|
|
|
|
|
To avoid expensive re-acquisition of resources. The resources retain their identity, are kept in some
|
|
|
|
|
fast-access storage, and are re-used to avoid having to acquire them again.
|
|
|
|
|
|
2019-12-07 20:01:13 +02:00
|
|
|
## Class diagram
|
2018-02-20 09:48:44 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
## Applicability
|
|
|
|
|
Use the Dirty Flag pattern when
|
|
|
|
|
|
|
|
|
|
* Repetitious acquisition, initialization, and release of the same resource causes unnecessary performance overhead.
|
|
|
|
|
|
|
|
|
|
## Credits
|
|
|
|
|
|
|
|
|
|
* [Design Patterns: Dirty Flag](https://www.takeupcode.com/podcast/89-design-patterns-dirty-flag/)
|
