Re: My thoughts on C# and gaming.

Hello,

> I don't see why you'd lose the safety. Because it's CLR-derived you
> don't need a conservative garbage collector. Thus, you can assert (in
> non-final builds) that no back pointers exist into that pool when you
> blow it away. Given that pool-blowing-awaying generally should only
> happen during loading time, that assert shouldn't get in the way much
> of regular play testing etc.

In this trivial sample:

	var foo = new Foo ();	// Allocate from Pool
	DisposeThePool ();
	foo.Dingus = 1;

The lack of safety is that the 3 statement is writing over memory that
has been released, something that would never happen under the safe
execution environment.

This shifts the responsibility of the safety from the language/runtime
to the developer.   It is perfectly fine to do something like this, but
the results is no longer a type safe environment.

Miguel.

_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com