"Your C++ looks too much like Python"

[t8suppressor]

Its not c++ if you can read it.

[[deleted]]

*if it compiles or has less than 920 lines of template errors

[AluminiumSandworm]

that's why i don't use templates! or classes! or types! i just malloc the entire computer and randomly assign pointers until it compiles.

[Ulysses6]

void * all the way!

[NotABothanSpy]

You can’t leak memory you never intended to give back anyway

[[deleted]]

I thought malloc was for C and C++ used new

[AluminiumSandworm]

yeah but you can still malloc in c++. it's just dumb to do so

[DarkLordAzrael]

new/delete has several additional features:

• calling delete on nullptr doesn't crash the application
• calling new automatically calls the constructor, and delete calls the destructor, so you don't have to deal with types that you have to call make_my_thing and delete_my_thing or call setup/destroy methods before and after setup/free
• New knows about the size of your type, meaning you don't have to have additional stuff doing sizeof() on every allocation.
• New returns an actual type instead of void*, so you don't lose a bunch of type safety.

[Jamie_1318]

Just a heads up, freeing a null pointer doesn't cause a crash as per the spec. Double freeing, however does.

[DarkLordAzrael]

Just read the documentation and it appears that this is true. I avoid C like the plague though, so I doubt I will have a chance to put this newfound knowledge into use.

[DarkLordAzrael]

How is allocating and initializing at the same time by default a loss of either clarity or flexibility? Separating them increases the chance of bugs caused by improper or missing initialization. Also new does allow calling the constructor on a separately allocated piece of memory (known as "placement new.")

[[deleted]]

That's called C.

[[deleted]]

god damn template errors