[Python-Dev] .clinic.c vs .c.clinic (original) (raw)
Ethan Furman ethan at stoneleaf.us
Mon Jan 20 21:05:55 CET 2014
- Previous message: [Python-Dev] .clinic.c vs .c.clinic
- Next message: [Python-Dev] .clinic.c vs .c.clinic
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 01/20/2014 11:46 AM, Brett Cannon wrote:
On Mon, Jan 20, 2014 at 2:09 PM, Barry Warsaw wrote:
On Jan 20, 2014, at 12:05 AM, Larry Hastings wrote:
Contestant 5: "Put in clinic directory, add .h"
foo.c -> clinic/foo.c.h foo.h -> clinic/foo.h.h This is cached output right? Yes, it's generated entirely based on data provided in original source file. IOW, it can be regenerated if it's missing. If so, this seems like a nice parallel to pycache. It's mostly hidden until you want to go looking for it. 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.
Won't AC put those macros in the source file for you?
--
Ethan
- Previous message: [Python-Dev] .clinic.c vs .c.clinic
- Next message: [Python-Dev] .clinic.c vs .c.clinic
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]