[issue25889] Find_BOM accepts a char*, but is passed an unsigned char*; and related usage

Roundup Robot added the comment: New changeset 2481ae1ce35c by Serhiy Storchaka in branch 'default': Issue #25889: Got rid of warning about mixing signed/unsigned char pointers. https://hg.python.org/cpython/rev/2481ae1ce35c -- nosy: +python-dev ___

[issue25889] Find_BOM accepts a char*, but is passed an unsigned char*; and related usage

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue25889] Find_BOM accepts a char*, but is passed an unsigned char*; and related usage

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka nosy: +serhiy.storchaka versions: +Python 3.6 ___ Python tracker ___

[issue25889] Find_BOM accepts a char*, but is passed an unsigned char*; and related usage

New submission from Alexander Riccio: This is safe, but warns on /W4. In maybe_handle_shebang, an unsigned char* is passed to find_BOM, which accepts a char* (https://hg.python.org/cpython/file/tip/PC/launcher.c#l1139). Without an explicit cast, this generates a warning: