Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

One word

Name: I are epic sage 2007-05-12 6:13 ID:YorH/OTc

In a world of qualified only pointers, many unsafe languages become safe.

Take for instance, the possible choices:
pushed * : pointer to <insert type> allocated on the stack
pooled * : pointer to <insert type> allocated on the heap
intern * : pointer to <insert type> local method allocation
extern * : pointer to <insert type> nonlocal method allocation

There are others, like method * and shared *, but they are hard to explain to n00bs.

Without generic one-type-fits-all pointers and the disallowance of casting between pointers, it would become impossible to manipulate instances of user defined classes. And, that's not all; many problems could be caught by a compiler that previously could not be.

Ha! Revel in my genius!

Name: Anonymous 2007-05-13 7:20 ID:47LL1JSS

>>4
Who said the language I am referring does not have automatic memory management? If you do it right, it is great; if not, it is massive phail.

intern Object pooled *o = new Object;

Deletes just before program termination ('intern' is same as static storage).

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List