<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">On Thursday 12 March 2009, Richard Dale wrote:<br>
> I think turning off virtual method callbacks during GC is more reliable.<br>
> But I had thought of caching the result for a virtual method callback test,<br>
> so it only has to be done once for an instance (or once per Ruby class<br>
> perhaps). It needs a bit more thought.<br>
Not sure if I did understood correctly what you want to cache :) But wouldn't that be a problem if the virtual function is added after the test ? Would the function still be called ? Or would the caching prevent that ?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> We could also change the smoke library code generation so that there would<br>
> be a flag for each virtual method call, and set that after the first test,<br>
> instead of testing each time.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
Cyrille Berger</p></body></html>