You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Martin Zink (Jira)" <ji...@apache.org> on 2023/03/09 15:45:00 UTC

[jira] [Updated] (MINIFICPP-2052) Ambigous signed/unsigned chars

     [ https://issues.apache.org/jira/browse/MINIFICPP-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Zink updated MINIFICPP-2052:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

https://github.com/apache/nifi-minifi-cpp/commit/06d5467c6ca2d9a20ca9a969fd768e03025c362d

> Ambigous signed/unsigned chars
> ------------------------------
>
>                 Key: MINIFICPP-2052
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-2052
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Bug
>            Reporter: Martin Zink
>            Assignee: Martin Zink
>            Priority: Major
>
> We currently rely on that the char type is signed. (this is usually the case on x86_64 systems, and on apple silicon aswell)
> But this is not guarenteed, since the standard does not specify if plain {{char}} is signed or unsigned.
> This can cause various issues on ARM systems where the char is unsigned by default. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)