On Thu, 03 Jul 2008, Ian Jackson wrote:
> * Suppressing lazy symbol resolution may work in this case, but it
> is not correct.
Lazy symbol resolution should be supressed while in eval regardless of
the method which we use to resolve this problem. Non-recoverable
failures from code in eval should be minimized to the extent possible.
While there are other API/ABI differences that may not be caught,
catching the obvious ones is better than catching none at all.
Don Armstrong
--
Love is... a complex sequence of neurochemical reactions that makes
people behave like idiots. It's similar to intoxication, but the
hangover's even worse.
-- J. Jacques _Questionable Content_ #1039
http://www.questionablecontent.net/view.php?comic=1039
http://www.donarmstrong.com http://rzlab.ucr.edu
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
