[
https://issues.apache.org/jira/browse/PROTON-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adel Boutros updated PROTON-1324:
---------------------------------
Attachment: 0010-SunStudio-Fix-the-interpretation-of-int8_t.patch
> Interpretation of "int8_t" on Solaris using SunStudio is different from GCC
> one
> -------------------------------------------------------------------------------
>
> Key: PROTON-1324
> URL: https://issues.apache.org/jira/browse/PROTON-1324
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
> Reporter: Adel Boutros
> Assignee: Cliff Jansen
> Attachments: 0010-SunStudio-Fix-the-interpretation-of-int8_t.patch
>
>
> Looking at the standard, there are actually 3 ways to define a char:
> * char
> * signed char
> * unsigned char
> There are no specificatoins regarding what "char" will be interperted as
> either "signed char" or "unsigned char". This is left to the OS/Compiler to
> choose.
> Solaris: int8_t --> char
> Linux: int8_t --> signed char
> You can check here: http://en.cppreference.com/w/cpp/language/types
> {quote}
> char - type for character representation which can be most efficiently
> processed on the target system (has the same representation and alignment as
> either signed char or unsigned char, but is always a distinct type).
> Multibyte characters strings use this type to represent code units.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
