<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>mikeash.com pyblog/friday-qa-2011-11-11-building-a-memoizing-block-proxy.html comments</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2011-11-11-building-a-memoizing-block-proxy.html#comments</link><description>mikeash.com Recent Comments</description><lastBuildDate>Sun, 12 Apr 2026 02:27:14 GMT</lastBuildDate><generator>PyRSS2Gen-1.0.0</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>mikeash - 2011-11-14 16:43:05</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2011-11-11-building-a-memoizing-block-proxy.html#comments</link><description>Good points, all. I guess you can tell that this is a proof of concept and not thoroughly tested code. Somehow it never occurred to me that a C string argument might be NULL.</description><guid isPermaLink="true">2ed61a894122f5f47a7a41fd06bb5f05</guid><pubDate>Mon, 14 Nov 2011 16:43:05 GMT</pubDate></item><item><title>KenThomases - 2011-11-12 06:18:56</title><link>http://www.mikeash.com/?page=pyblog/friday-qa-2011-11-11-building-a-memoizing-block-proxy.html#comments</link><description>You leak the copy in the NSCopying special case.
&lt;br /&gt;
&lt;br /&gt;For both the arguments and return value, if the type is a C string but the value is NULL, you pass that NULL to strlen(), which will blow up.  And if it doesn't blow up, you pass it to -[NSData dataWithBytes:length:], too.</description><guid isPermaLink="true">c511c2ada46c01930756a587c3d8e0a1</guid><pubDate>Sat, 12 Nov 2011 06:18:56 GMT</pubDate></item></channel></rss>
