Message203618
| Author |
ncoghlan |
| Recipients |
Arfrever, eric.snow, georg.brandl, ncoghlan, serhiy.storchaka, vstinner |
| Date |
2013年11月21日.12:04:49 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1385035489.39.0.958202018909.issue19518@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
How about "ExName"?
This patch:
PyRun_AnyFileExName
PyRun_SimpleFileExName
PyRun_InteractiveOneExName
PyRun_InteractiveLoopExName
PyRun_FileExName
Previous patch:
Py_CompileStringExName
PyAST_FromNodeExName
PyAST_CompileExName
PyFuture_FromASTExName
PyParser_ParseFileExName
PyParser_ParseStringExName
PyErr_SyntaxLocationExName
PyErr_ProgramTextExName
PyParser_ASTFromStringExName
PyParser_ASTFromFileExName
- "Ex" has precedent as indicating a largely functionally equivalent API with a different signature
- "Name" suggests strongly that we're tinkering with the filename (since this APIs don't accept another name)
- "ExName" is the same length as "Object" but far more explicit
Thoughts? |
|