On 01/14/2014 05:32 PM, Ryan Smith-Roberts wrote: > Pondering it this afternoon, I thought of a configuration that > minimizes both code churn and readability impact: two buffers. One at > the top containing forward declarations and defines (an inline header > file if you like), and the rest of the autogenerated code at the > bottom. It's not obvious that AC currently supports this > configuration, or backtracking of any kind. Clinic is strictly one pass currently. I could add this feature to the prototype if there was sufficient interest; for now, I'd accept a patch to the clinic-buffer-samples repo adding a sample of your proposal. Please start with "_pickle.original.c", and add simulated (but deliberately invalid!) Clinic instructions for an authentic flair. I suggest the name "forward" for the destination, and "_pickle.using-forward.buffer.c" for the filename. I take it "forward" would get the methoddef_define, the docstring_prototype, and the parser_prototype, "block" would get the impl_prototype, and "buffer" would get the docstring_definition and the parser_definition? I'm happy to collect votes for this approach too. I'll put you down as a +1 //arry/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140114/b4291355/attachment.html>
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