[reSIProcate] Compilation error in latest code
david Butcher
david at purplecomm.com
Tue Nov 23 12:20:51 CST 2004
Quoting Alan Hawrylyshen <alan at jasomi.com>:
[snip]
> Actually that's not too bad and might make a strong case for removing
> the complicated frame-local initial buffer code from Data. What do you
> think?
> Then again, maybe not -- any thoughts on this matter?
Yeah, I thought about this. I decided that the internal buffer is appropriately
syntactically free. It finesses small data management without involving the
caller which is likely where the caller doesn't want to think about memory
management.
Playing around explicitly with the stack is appropriately syntactically awkward.
It will be used (hopefully) only after some deliberation.
Of course, those who decide that stack memory usage is way cool can compile out
the internal buffer and Borrow to their heart's content.
david
More information about the resiprocate-devel
mailing list