8,061 reputation
1845
bio website
location Los Angeles, CA
age
visits member for 4 years, 8 months
seen 6 hours ago

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.


1d
revised How would you structure your code for a Neural Network?
added 132 characters in body
May
21
revised Blocking function call with asynchronous content
added 153 characters in body
May
21
revised Blocking function call with asynchronous content
added 603 characters in body
May
18
revised Is there any advantage to c-style bit manipulation over std::bitset?
added 1110 characters in body
May
16
revised How do you pass or fail performance tests?
added 860 characters in body
May
3
revised Design of actions handlers requiring some order
added 85 characters in body
May
3
revised What characteristics does software have that's easily modified by other developers 6+ months after initial release?
added 675 characters in body
Apr
30
revised Thread priorites - how to?
added 49 characters in body
Apr
30
revised Thread priorites - how to?
added 2207 characters in body
Apr
29
revised Compile-time vs. run-time configuration
added 1475 characters in body
Apr
28
revised fast, say O(log2(N)), sliding median algorithm
added 362 characters in body
Apr
26
revised Are there real world examples demonstrating reasonable performance improvement by using move semantics?
added 1158 characters in body
Apr
26
revised Are there real world examples demonstrating reasonable performance improvement by using move semantics?
added 1158 characters in body
Apr
17
revised Why was the Itanium processor difficult to write a compiler for?
added 808 characters in body
Apr
17
revised Why was the Itanium processor difficult to write a compiler for?
added 808 characters in body
Apr
17
revised Why was the Itanium processor difficult to write a compiler for?
added 808 characters in body
Apr
17
revised Why was the Itanium processor difficult to write a compiler for?
added 906 characters in body
Apr
17
revised Why was the Itanium processor difficult to write a compiler for?
added 1494 characters in body
Apr
7
revised No exceptions C++ and partially constructed objects
Added mandatory disclaimer point 2.
Apr
6
revised Where should I place a typedef when used in method signatures in C++?
added 227 characters in body