Occasionally one encounters the suggestion that a garbagecol

Occasionally one encounters the suggestion that a garbage-collected language should provide a delete operation as an optimization: by explicitly deleting objects that will never be used again, the programmer might save the garbage collector the trouble of finding and reclaiming these objects automatically, thereby improving performance. What do you think of this suggestion? Explain. Alternatively, one might allow the programmer to \"tenure\" an object, so that it will never be a candidate for reclamation. Is this a good idea?

Solution

a) the logic is good as the objects or variables which are not being used in program simple use to waste memory so to provide a delete operation( deleting an item explicitly after its work is done) or some logic that whenever any object or variable task gets completed it automatically gets deleted from the memory. this will help in the less wastage of memory and the complexity of the program can increase a little bit but efficiency of a program and memory will ne faster .

b)