It will call delete[] and hence the entire array will be reclaimed but I believe you need to indicate that you are using an array form of unique_ptrby: std::unique_ptr<int[]> my_array(new int[5]); This is called as Partial Specialization of the unique_ptr.
This expression: CPlayer(position, attacker) creates a temporary object of type CPlayer using the above constructor, then: CPlayer newPlayer =…; The mentioned temporary object gets copied using the copy constructor to newPlayer. A better way is to write the following to avoid temporaries: CPlayer newPlayer(position, attacker);
For general programming, yes you should use new and delete. However, if you are writing a library, you should not! I don’t have your textbook, but I imagine it is discussing allocators in the context of writing library code. Users of a library may want control over exactly what gets allocated from where. If all … Read more
In general, if something is documented as being a constructor, use new with it. But in this case, RegExp has a defined “factory” behavior for the situation where you’ve called it as a function instead. See Section 15.10.3 of the ECMAScript (JavaScript) specification (that links to the outgoing spec; the section number is the same … Read more
Isn’t this the normal way to free the memory associated with an object? This is a common way of managing dynamically allocated memory, but it’s not a good way to do so. This sort of code is brittle because it is not exception-safe: if an exception is thrown between when you create the object and … Read more
The alignment has the following guarantee from the standard (3.7.3.1/2): The pointer returned shall be suitably aligned so that it can be converted to a pointer of any complete object type and then used to access the object or array in the storage allocated (until the storage is explicitly deallocated by a call to a … Read more
You can just iterate over the keys and invoke the setters. I prefer this, because it will catch if you pass an invalid key. class Foo attr_accessor :name, :age, :email, :gender, :height def initialize params = {} params.each { |key, value| send “#{key}=”, value } end end foo = Foo.new name: ‘Josh’, age: 456 foo.name … Read more
This is a possible solution. It will always choose the operator with the highest alignment in a given hierarchy: #include <exception> #include <iostream> #include <cstdlib> // provides operators for any alignment >= 4 bytes template<int Alignment> struct DeAllocator; template<int Alignment> struct DeAllocator : virtual DeAllocator<Alignment/2> { void *operator new(size_t s) throw (std::bad_alloc) { std::cerr << … Read more
In your example, the Red Car instance of c will become eligible for garbage collection when c is assigned to Blue Car. You don’t need to do anything. Check out this (old, but still relevant) MSDN article about the .NET garbage collector. http://msdn.microsoft.com/en-us/magazine/bb985010.aspx The first paragraph says it all: Garbage collection in the Microsoft .NET … Read more
Bala’s answer is correct, but it might be helpful to see why you’d want to do this. Consider the problem that the BCL designers were faced with when designing the libraries for CLR version 2. There was an existing interface: interface IEnumerable { IEnumerator GetEnumerator(); } Now you want to add: interface IEnumerable<T> : IEnumerable … Read more