[Python-Dev] .clinic.c vs .c.clinic
Ethan Furman
ethan at stoneleaf.us
Mon Jan 20 23:52:13 CET 2014
More information about the Python-Dev mailing list
Mon Jan 20 23:52:13 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 01:57 PM, Larry Hastings wrote: > > If that's what you meant, then: yes, and yes. It's possible to skip the second pass if you're comfortable guessing the > generated name of the macro, but that's just one more thing for people to remember, and hunting for it is easier. And > yes, whether it's original output or buffer or "clinic file" (I'm trying to deprecate the name "side file", it was a > dumb idea), the destination Argument Clinic writes to doesn't dramatically alter what it writes. Okay, thanks. And I'm happy to call them clinic files. :) -- ~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 ]
More information about the Python-Dev mailing list