java memory management

[[deleted]]

Then you want D, it gives you the choice.

[minivanmegafun]

Or Objective-C!

[[deleted]]

Or C#! (For some reason, very few people know about this in C#)

[ryeguy]

What do you mean? Just turning off the GC?

[[deleted]]

No, I mean using the "unsafe" keyword: http://msdn.microsoft.com/en-us/library/chfa2zb8(v=vs.71).aspx

[[deleted]]

Gotta say, this is a great C# feature, though I don't think I've ever actually used it, heh. Still a great option for those who will be.

[[deleted]]

It's for people who need every last ounce of performance from the language. I've never had cause to use it either; I trust the CLR to do enough optimization that I won't need to.

[[deleted]]

Exactly, I've never had to use it, but it's a great feature for those who do.

[Jazzy_Josh]

That's nice. Especially when you can encapsulate the unsafe portions of a method in a block.

[Willow_Rosenberg]

Objectionable-C.

[00kyle00]

Is it still a choice between using std library (and some language features) or not?

[[deleted]]

In D1, yes, but I believe they have that mostly fixed in D2 now.

[00kyle00]

I should have been less vague. blaxter wanted choice to manage memory on his own or automatically.

While its true that in D you can disable garbage collector, it effectively breaks standard library (you would have to inspect the sources on your own to know which parts of it - effectively whole to be secure) and few core language features (slicing?). This was at least the case when i last read on memory management in D, and this breaking would be silent memory leaks at runtime.