Forums before death by AOL, social media and spammers... "We can't have nice things"
|    sci.electronics.design    |    Electronic circuit design    |    143,102 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 142,949 of 143,102    |
|    bitrex to Don Y    |
|    Re: Call by reference protection    |
|    20 Feb 26 17:25:35    |
      From: user@example.net              On 2/20/2026 12:47 PM, Don Y wrote:              > I use CoW to implement call-by-value semantics on objects that       > would typically be passed as call-by-reference. E.g., imagine       > anObject is a single frame of video and operator() is going to       > apply a masking function to it, eliding all but the "important"       > parts of the frame for return to the caller.       Similar to how GPUs do, if the operator() can perform its required       calculations on a const reference to the data but its output can be       reduced to operations on individual pixel values of integral type which       don't depend on the output value of neighboring pixels std::atomic is       for that situation, and should be lock free for processors that have       hardware support for atomics e.g. ARM v6 and later              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca