The traditional notion of object ownership via function call (i.e. where it is unconditionally and unquestionably assumed that the caller must own the object throughout the call, and the callee merely "borrows" from it) is detrimental to memory usage if the object passed via the call needs to be released early, in the middle of the call.
In the past, I may have blamed it on other things, but now I see it this way. And this faulty dogma is pandemic; I can't think of any language that escapes from it.
Top Network Posts
- 27why is 1>>32 == 1?
- 18OpenCV - approxPolyDP for edge maps (not contours)
- 15Fostering a time period where everyone can try any ideas to make software run faster?
- 14How to deal with "software end-of-life" situations?
- 14Why was the Itanium processor difficult to write a compiler for?
- 14Downsampling an image by an integer factor
- 13Specific reasons to create own array class over using std::array?
- View more network posts →