<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.omnivision.website/index.php?action=history&amp;feed=atom&amp;title=9.5.1_Creational_%28Singleton%2C_Factory%29</id>
	<title>9.5.1 Creational (Singleton, Factory) - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.omnivision.website/index.php?action=history&amp;feed=atom&amp;title=9.5.1_Creational_%28Singleton%2C_Factory%29"/>
	<link rel="alternate" type="text/html" href="https://wiki.omnivision.website/index.php?title=9.5.1_Creational_(Singleton,_Factory)&amp;action=history"/>
	<updated>2026-08-23T01:25:48Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.9</generator>
	<entry>
		<id>https://wiki.omnivision.website/index.php?title=9.5.1_Creational_(Singleton,_Factory)&amp;diff=307&amp;oldid=prev</id>
		<title>Mr. Goldstein: Created page with &quot;=== 9.5.1 Creational (Singleton, Factory) === Creational design patterns are all about how objects are created. They help make sure objects are created in a flexible and organized way.  * &#039;&#039;&#039;Singleton:&#039;&#039;&#039; Imagine you have a school, and there&#039;s only &#039;&#039;one&#039;&#039; principal. It wouldn&#039;t make sense to have two principals, right? A Singleton pattern ensures that a class can only have &#039;&#039;one&#039;&#039; instance (one copy) of itself throughout the entire program. This is useful when you need...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.omnivision.website/index.php?title=9.5.1_Creational_(Singleton,_Factory)&amp;diff=307&amp;oldid=prev"/>
		<updated>2025-07-10T02:56:07Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;=== 9.5.1 Creational (Singleton, Factory) === Creational design patterns are all about how objects are created. They help make sure objects are created in a flexible and organized way.  * &amp;#039;&amp;#039;&amp;#039;Singleton:&amp;#039;&amp;#039;&amp;#039; Imagine you have a school, and there&amp;#039;s only &amp;#039;&amp;#039;one&amp;#039;&amp;#039; principal. It wouldn&amp;#039;t make sense to have two principals, right? A Singleton pattern ensures that a class can only have &amp;#039;&amp;#039;one&amp;#039;&amp;#039; instance (one copy) of itself throughout the entire program. This is useful when you need...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;=== 9.5.1 Creational (Singleton, Factory) ===&lt;br /&gt;
Creational design patterns are all about how objects are created. They help make sure objects are created in a flexible and organized way.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Singleton:&amp;#039;&amp;#039;&amp;#039; Imagine you have a school, and there&amp;#039;s only &amp;#039;&amp;#039;one&amp;#039;&amp;#039; principal. It wouldn&amp;#039;t make sense to have two principals, right? A Singleton pattern ensures that a class can only have &amp;#039;&amp;#039;one&amp;#039;&amp;#039; instance (one copy) of itself throughout the entire program. This is useful when you need to control access to a single resource, like a settings manager for a game or a single database connection.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Factory:&amp;#039;&amp;#039;&amp;#039; Think of a toy factory. You tell the factory, &amp;quot;I need a car toy,&amp;quot; or &amp;quot;I need a doll toy,&amp;quot; and the factory builds it for you. You don&amp;#039;t need to know all the tiny steps involved in making each toy. The Factory pattern provides a way to create objects without specifying the exact type of object that will be created. It&amp;#039;s like having a special method that decides which kind of object to make based on your request, hiding the complex creation process from you.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Bibliography:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
* Gamma, Erich, Helm, Richard, Johnson, Ralph, and Vlissides, John. &amp;#039;&amp;#039;Design Patterns: Elements of Reusable Object-Oriented Software&amp;#039;&amp;#039;. Addison-Wesley Professional, 1994.&lt;/div&gt;</summary>
		<author><name>Mr. Goldstein</name></author>
	</entry>
</feed>