Re: [pcre-dev] size of pcre_uint32 and pcre_int32

Top Page
Delete this message
Author: Zoltán Herczeg
Date:  
To: Ze'ev Atlas
CC: Pcre Exim
Subject: Re: [pcre-dev] size of pcre_uint32 and pcre_int32
Hi,

yes, pcre_int32 and pcre_uint32 are always 32 bit long. However, there are other types: int_fast32_t / int_least32_t which might be more than 32 bit long and provides faster 32 bit computation. PCRE does not use them (at the moment).

See here: http://www.nongnu.org/avr-libc/user-manual/group__avr__stdint.html

Regards,
Zoltan

"Ze'ev Atlas" <zatlas1@???> írta:
>Hi PhilYou know that no good deed is going unpunished :)
>While my PCRE port for z/OS did not prove to be too popular (nevertheless, I am supporting it and plan to do PCRE2 when I am sure it is stable enough,) the off shoot of COBOL support is getting somewhat popular on platforms that ARE NOT z/OS (i.e. Linux and Windows).  To that end I have to make my copybooks (analogous to header files in C) compatible with those environments, especially 32 bits vs. 64 bits versions.
>PCRE in my opinion is well written in that it does not leave too much to chance and the header files explicitly specify types such as pcre_int8, pcre_uint8, etc.  My specific question is about the types pcre_int32 and pcre_uint32.  I looked at the pcre_internal.h and with my less then optimal knowledge of C, I could not determine the answer.  So explicitly, are those types guaranteed to always be 32 bits, no matter what, or could they be 64 bits on some occasions?  I hope that they are 32 bits no matter what.
>You could only imagine the grief that the GNU POSIX header files cause me because they are not as specific (I also ported the GNU header regex.h to COBOL).  I have to actually create two versions and give the poor users some convoluted instructions on what set of copybooks to use under what circumstances!
> Ze'ev Atlas
>
>--
>## List details at https://lists.exim.org/mailman/listinfo/pcre-dev