Showing content from http://mail.python.org/pipermail/python-dev/attachments/20140120/8adeedaf/attachment.html below:
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 20, 2014 at 2:09 PM, Barry Warsaw <span dir="ltr"><<a href="mailto:barry@python.org" target="_blank">barry@python.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Jan 20, 2014, at 12:05 AM, Larry Hastings wrote:<br>
<br>
>Contestant 5: "Put in __clinic__ directory, add .h"<br>
><br>
> Â Â foo.c -> __clinic__/foo.c.h<br>
> Â Â foo.h -> __clinic__/foo.h.h<br>
<br>
</div>This is cached output right?</blockquote><div><br></div><div>Yes, it's generated entirely based on data provided in original source file.</div><div>Â </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 IOW, it can be regenerated if it's missing.  If<br>
so, this seems like a nice parallel to __pycache__. Â It's mostly hidden until<br>
you want to go looking for it.<br></blockquote><div><br></div><div>More-or-less. The key difference is you will most likely look at the generated file *once* to copy-and-paste the relevant macros to paste into your source file for use (e.g. the relevant MethodDef stuff). But it's a one-time thing that never has to be done again as long as you don't rename a function or method.</div>
</div></div></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4