On Oct 13, 2011, at 08:08 PM, Martin v. Löwis wrote: >>> Py_CONST_STRING or Py_IDENTIFIER would be fine with me. Given that >>> everything else uses "Id" in their name, Py_IDENTIFIER is probably better? >> >> I agree that either is fine, with a slight preference for Py_IDENTIFIER for >> the same reasons. > >Ok, so it's Py_IDENTIFIER. Given below, shouldn't that be _Py_IDENTIFIER? >>>> So I think it needs a prefix. If you don't like PyId_, let me know >>>> what the prefix should be instead. >>> >>> I agree with that. >> >> I'm fine with that too, as long as it's all well-documented in the C API >> guide. > >Hmm. People voted that this should be an internal API, so I'm not sure it should be documented at all outside of the header file, or if, in >what document. > >Currently, this very point is documented in the header file. That's fine, if the macro is prefixed with an underscore. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20111013/8e867136/attachment.pgp>
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