[Python-Dev] Nuking wstr [Re: How can we use 48bit pointer safely?] (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Sat Mar 31 05:35:10 EDT 2018
- Previous message (by thread): [Python-Dev] Nuking wstr [Re: How can we use 48bit pointer safely?]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 30 Mar 2018 21:40:21 +0300 Serhiy Storchaka <storchaka at gmail.com> wrote:
30.03.18 16:54, Antoine Pitrou пише: > We could also simply nuke wstr. I frankly don't think it's very > important. It's only used when calling system functions taking a > wchart argument, as an « optimization ». I'd be willing to > guess that modern workloads aren't bottlenecked by the cost overhead of > those system functions...
This is possible only after removing all PyUNICODE related C API. It is deprecated since 3.3, but only in the documentation, and should stay to the EOL of 2.7. Only in 3.7 most of these functions started emitting deprecation warnings at compile time (GCC-only). [1] It would be good to make them emitted in other compilers too.
It should be possible with MSVC: https://stackoverflow.com/a/295229/10194
and clang as well: http://releases.llvm.org/3.9.1/tools/clang/docs/AttributeReference.html#deprecated-gnu-deprecated
Regards
Antoine.
- Previous message (by thread): [Python-Dev] Nuking wstr [Re: How can we use 48bit pointer safely?]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]