--- Comment #21 from BCS <>  2009-07-30 14:35:05 PDT 
(In reply to comment #19)
> (In reply to comment #17)
> > 
> > You assume that the above is a bug and what I really wanted was to return a
> > reference. Take another look while assuming that I actual do want return by
> > value and the return by reference would be a bug.
> I suppose what caught me is that it's easily possibly to write
> GetProcessOutput() such that a ref return isn't a bug.  Just make sure the
> reference doesn't point to an OutputHandle that's already in use.  I feel like
> having a value return there is unnecessary.  

In most cases you are probably correct but, while I can't enumerate a specific
example, I can imagine a cases where the value return us wanted for it's
semantics rather than for memory usage reasons. For instance something in the
direction of  smart pointers or keeping track of distinct handles to a common

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to