Message287156
| Author |
vstinner |
| Recipients |
scoder, serhiy.storchaka, skrah, vstinner |
| Date |
2017年02月06日.17:15:38 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1486401339.08.0.779237982487.issue29464@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> We can avoid breaking backward compatibility and introduce new call method METH_FASTCALL_NO_KEYWORDS. But combining existing flags looks better to me. FASTCALL is not a part of stable ABI.
If we decide that having two FASTCALL calling convention, I prefer what you proposed: METH_FASTCALL (pos only) and METH_FASTCALL|METH_KEYWORDS (pos+kw). As you wrote, I like reusing the existing METH_KEYWORDS flag, it reduces the surprises if someone ports existing code using METH_VARARGS and METH_VARARGS|METH_KEYWORDS. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2017年02月06日 17:15:39 | vstinner | set | recipients:
+ vstinner, scoder, skrah, serhiy.storchaka |
| 2017年02月06日 17:15:39 | vstinner | set | messageid: <1486401339.08.0.779237982487.issue29464@psf.upfronthosting.co.za> |
| 2017年02月06日 17:15:39 | vstinner | link | issue29464 messages |
| 2017年02月06日 17:15:38 | vstinner | create |
|