new = singleton

#1 I think the problem with new is that it overwrites the old. With singleton another attempt to create the same thing is just dropped and returns the originally generated one

#2 @Steve - Brief Singleton Syntax.

Let's say you have the following:

new ShaderData( SSAOShader )
{   
   DXVertexShaderFile 	= "shaders/common/postFx/postFxV.hlsl";
   DXPixelShaderFile 	= "shaders/common/postFx/ssao/SSAO_P.hlsl";            
   pixVersion = 3.0;
};

If you were to perform another new ShaderData(SSAOShader), the second one will fail to create. Now, if you are using singletons, it's a different story. If you create a second singleton ShaderData(SSAOShader), the properties of the second object will update/override the original.

#3 michael,
.. that's how new used to behave in TGE, ennit ?

#4 @Orion - I know it did not fully support what the singleton keyword can do. It may have completely overridden instead of just updating.

#5 yes.. it does seem different.
in TGE, if you issued a second New with the same object name,
it created a new object and assigned the global name to it.

so both objects would report their name the same, and answer to the same namespace, but referencing the global name would reference the latter.

this was sometimes hell and sometimes convenient.

interesting, this new stuff. ;)