How should I print types like off_t and size_t?
Asked Answered
I

10

160

I'm trying to print types like off_t and size_t. What is the correct placeholder for printf() that is portable?

Or is there a completely different way to print those variables?

Invercargill answered 25/2, 2009 at 17:11 Comment(2)
@devin: I believe I've found that type while using fopen, fseek, etc. on Mac OS X. off_t is used for the offset.Anson
What's the correct way to use printf to print a size_t?Thyroiditis
M
123

You can use z for size_t and t for ptrdiff_t like in

printf("%zu %td", size, ptrdiff);

But my manpage says some older library used a different character than z and discourages use of it. Nevertheless, it's standardized (by the C99 standard). For those intmax_t and int8_t of stdint.h and so on, there are macros you can use, like another answer said:

printf("value: %" PRId32, some_int32_t);
printf("value: %" PRIu16, some_uint16_t);

They are listed in the manpage of inttypes.h.

Personally, I would just cast the values to unsigned long or long like another answer recommends. If you use C99, then you can (and should, of course) cast to unsigned long long or long long and use the %llu or %lld formats respectively.

Molecule answered 25/2, 2009 at 17:38 Comment(13)
Since PRId32 doesn't include the % format specifier, shouldn't that be printf("value: %" PRId32, some_int32_t);Recliner
off_t is actually a signed long long on my system.Anson
yeah for signed values you will have to convert to long or long long. this latter type does not exist in current C++ - but next version includes it. especially if you work with posix and it includes some types like off_t that have big sizes, you've to be careful.Molecule
then, i would use long long and proper formats if you know it supports long long. otherwise for embedded development where you know you only have to do with long as widest type, you can stick with long/unsigned long.Molecule
this question is about C. i forgot that. so i better mention in the answer that if you have long long available (as in c99) you should use that.Molecule
I think the man page discourages use of Z (uppercase) which was used by libc5. It doesn't seem to discourage z (lowercase).Brno
Using %zd with a size_t is undefined behavior due to the signedness mismatch (C99 7.19.6.1#9). It must be %zu.Osher
Well, how to print off_t then?Caenogenesis
Very important Note: %zd and %zu don't work at visual studio 2010 - your application will CRASH! You should rather use %Iu (not L, it is big i). For more types see this: msdn.microsoft.com/en-us/library/tcxf1dw6(v=vs.100).aspxBarnardo
@Osher I don’t see how %zd with a size_t gets undefined behaviour from that paragraph or from any other. In fact, the definition of %z in #7 explicitly allows %d with size_t and the corresponding signed type, and §6.2.5#9 explicitly allows using values of unsigned types where the corresponding signed type is expected, as long as the value is a valid nonnegative value of the signed type.Woodman
@JohannesSchaub-litb You say "You can use z" but below it says "%zu". What does that mean, for a noob like me? I googled and "u" means unsigned. Why didn't you write "You can use zu" intead?Gotten
@Gotten when I mentioned z and t, (the second one actually should be %td), I referred to modifiers. Like you say, u means unsigned, and d means signed. size_t exist in signed and unsigned versions (size_t and ssize_t). The important information is z, as it means "signed or unsigned size_t". Had you written %lu it meant long signed, for example. Google for man 3 printf.Molecule
@JohannesSchaub-litb How is %lu long signed? When you say: Had you written ... it meant ...' I would also argue that size_t doesn't have more than one version; rather it's a typedef though I guess if you call signed versus unsigned 'versions' you could argue that size_t and ssize_t are versions.Etna
R
130

To print off_t:

printf("%jd\n", (intmax_t)x);

To print size_t:

printf("%zu\n", x);

To print ssize_t:

printf("%zd\n", x);

See 7.19.6.1/7 in the C99 standard, or the more convenient POSIX documentation of formatting codes:

http://pubs.opengroup.org/onlinepubs/009695399/functions/fprintf.html

If your implementation doesn't support those formatting codes (for example because you're on C89), then you have a bit of a problem since AFAIK there aren't integer types in C89 that have formatting codes and are guaranteed to be as big as these types. So you need to do something implementation-specific.

For example if your compiler has long long and your standard library supports %lld, you can confidently expect that will serve in place of intmax_t. But if it doesn't, you'll have to fall back to long, which would fail on some other implementations because it's too small.

Rissa answered 9/3, 2011 at 20:44 Comment(5)
This is by far the better answer, I would have forgotten about using %zu for unsigned size_t. And casting to intmax_t is a great solution to whatever off_t is on any platform.Angle
POSIX doesn't guarantee that ssize_t has the same size as size_t, so truly portable code should convert it to intmax_t and print with %jd just like off_t.Burnt
off_t can be upto size long long and can be variable depending on defines... Visual Studio warns with this also "warning C4477: '_snprintf_s' : format string '%jd' requires an argument of type '__int64', but variadic argument 1 has type 'off_t'"... A truely portable way is printf("%lld\n", (long long)x);Moselle
amazing.........Elviraelvis
i would add this information can be found in $ man 2 printfElviraelvis
M
123

You can use z for size_t and t for ptrdiff_t like in

printf("%zu %td", size, ptrdiff);

But my manpage says some older library used a different character than z and discourages use of it. Nevertheless, it's standardized (by the C99 standard). For those intmax_t and int8_t of stdint.h and so on, there are macros you can use, like another answer said:

printf("value: %" PRId32, some_int32_t);
printf("value: %" PRIu16, some_uint16_t);

They are listed in the manpage of inttypes.h.

Personally, I would just cast the values to unsigned long or long like another answer recommends. If you use C99, then you can (and should, of course) cast to unsigned long long or long long and use the %llu or %lld formats respectively.

Molecule answered 25/2, 2009 at 17:38 Comment(13)
Since PRId32 doesn't include the % format specifier, shouldn't that be printf("value: %" PRId32, some_int32_t);Recliner
off_t is actually a signed long long on my system.Anson
yeah for signed values you will have to convert to long or long long. this latter type does not exist in current C++ - but next version includes it. especially if you work with posix and it includes some types like off_t that have big sizes, you've to be careful.Molecule
then, i would use long long and proper formats if you know it supports long long. otherwise for embedded development where you know you only have to do with long as widest type, you can stick with long/unsigned long.Molecule
this question is about C. i forgot that. so i better mention in the answer that if you have long long available (as in c99) you should use that.Molecule
I think the man page discourages use of Z (uppercase) which was used by libc5. It doesn't seem to discourage z (lowercase).Brno
Using %zd with a size_t is undefined behavior due to the signedness mismatch (C99 7.19.6.1#9). It must be %zu.Osher
Well, how to print off_t then?Caenogenesis
Very important Note: %zd and %zu don't work at visual studio 2010 - your application will CRASH! You should rather use %Iu (not L, it is big i). For more types see this: msdn.microsoft.com/en-us/library/tcxf1dw6(v=vs.100).aspxBarnardo
@Osher I don’t see how %zd with a size_t gets undefined behaviour from that paragraph or from any other. In fact, the definition of %z in #7 explicitly allows %d with size_t and the corresponding signed type, and §6.2.5#9 explicitly allows using values of unsigned types where the corresponding signed type is expected, as long as the value is a valid nonnegative value of the signed type.Woodman
@JohannesSchaub-litb You say "You can use z" but below it says "%zu". What does that mean, for a noob like me? I googled and "u" means unsigned. Why didn't you write "You can use zu" intead?Gotten
@Gotten when I mentioned z and t, (the second one actually should be %td), I referred to modifiers. Like you say, u means unsigned, and d means signed. size_t exist in signed and unsigned versions (size_t and ssize_t). The important information is z, as it means "signed or unsigned size_t". Had you written %lu it meant long signed, for example. Google for man 3 printf.Molecule
@JohannesSchaub-litb How is %lu long signed? When you say: Had you written ... it meant ...' I would also argue that size_t doesn't have more than one version; rather it's a typedef though I guess if you call signed versus unsigned 'versions' you could argue that size_t and ssize_t are versions.Etna
W
5

For Microsoft, the answer is different. VS2013 is largely C99 compliant but "[t]he hh, j, z, and t length prefixes are not supported." For size_t "that is, unsigned __int32 on 32-bit platforms, unsigned __int64 on 64-bit platforms" use prefix I (capital eye) with type specifier o, u, x, or X. See VS2013 Size specification

As for off_t, it is defined as long in VC\include\sys\types.h.

Watchword answered 20/3, 2014 at 15:39 Comment(1)
Note if off_t is always long that would make it 32-bit (even 64-bit Windows uses 32-bit for long).Izmir
I
4

You'll want to use the formatting macros from inttypes.h.

See this question: Cross platform format string for variables of type size_t?

Inanity answered 25/2, 2009 at 17:39 Comment(3)
Assuming that off_t is a signed, pointer-sized int (I don't know what the precise definition is) like ptrdiff_t then you'd use PRIdPTR or PRIiPTR.Inanity
The off_t type is larger than a pointer on any 32-bit system that supports large files (which is most 32-bit systems these days).Mental
@DietrichEpp: Actually, it's worse than that; many 32-bit systems have both off_t and off64_t, and depending on the feature macros off_t may actually mean off64_t.Malek
B
3

Which version of C are you using?

In C90, the standard practice is to cast to signed or unsigned long, as appropriate, and print accordingly. I've seen %z for size_t, but Harbison and Steele don't mention it under printf(), and in any case that wouldn't help you with ptrdiff_t or whatever.

In C99, the various _t types come with their own printf macros, so something like "Size is " FOO " bytes." I don't know details, but that's part of a fairly large numeric format include file.

Billiards answered 25/2, 2009 at 17:20 Comment(0)
S
1

Looking at man 3 printf on Linux, OS X, and OpenBSD all show support for %z for size_t and %t for ptrdiff_t (for C99), but none of those mention off_t. Suggestions in the wild usually offer up the %u conversion for off_t, which is "correct enough" as far as I can tell (both unsigned int and off_t vary identically between 64-bit and 32-bit systems).

Sooksoon answered 25/2, 2009 at 17:37 Comment(2)
My system (OS X) has 32-bit unsigned int and 64-bit off_t. So the cast would cause data to be lost.Mental
POSIX specifies that off_t has to be a signed type, so I wouldn't recommend this.Eras
H
1

If you use C11 or C18, you can use _Generic.

#include <stdio.h>
#include <sys/types.h>

    #define TYPE_FORMAT(variable) _Generic \
      (                                    \
        (variable)                         \
        , unsigned char       : "%hhu"     \
        , unsigned short      : "%hu"      \
        , unsigned int        : "%u"       \
        , unsigned long       : "%lu"      \
        , unsigned long long  : "%llu"     \
        , signed   char       : "%hhi"     \
        , signed   short      : "%hi"      \
        , signed   int        : "%i"       \
        , signed   long       : "%li"      \
        , signed   long long  : "%lli"     \
      )
      
      
int main(void)
  {
    off_t a=3321;
    printf(TYPE_FORMAT(a), a);
  }
      

However, there is one major drawback: You can not combine strings this way. Means this:

printf("Foo: " TYPE_FORMAT(a), a);

will not work, which makes it useless for many situation. Yes you could combine the string during runtime but that is annoying.

Hessite answered 30/7, 2021 at 21:16 Comment(0)
C
-3

I saw this post at least twice, because the accepted answer is hard to remeber for me(I rarely use z or j flags and they are seems not platform independant).

The standard never says clearly the exact data length of size_t, so I suggest you should first check the length size_t on your platform then select one of them:

if sizeof(size_t) == 4 use PRIu32
if sizeof(size_t) == 8 use PRIu64

And I suggest using stdint types instead of raw data types for consistancy.

Convexoconcave answered 14/10, 2016 at 8:30 Comment(1)
For C99 and C11, the standard explicitly states that %zu can be used to print size_t values. One should definitely not resort to using a uint32_t/uint64_t format specifier to print a size_t, as there's no guarantee that those types are compatible.Mouldy
O
-4

As I recall, the only portable way to do it, is to cast the result to "unsigned long int" and use %lu.

printf("sizeof(int) = %lu", (unsigned long) sizeof(int));
Oxheart answered 25/2, 2009 at 17:20 Comment(3)
Should be "%lu", as the length modifier should come before the conversion.Sooksoon
off_t for example is a signed long long.Anson
@GeorgSchölly - Then you've hit a conundrum, because long long does not exist in the C++ standard, and is thus inherently non-portable.Oxheart
T
-9

use "%zo" for off_t. (octal) or "%zu" for decimal.

Talented answered 26/3, 2010 at 11:19 Comment(1)
Why would you want the file offset in octal?Acosmism

© 2022 - 2024 — McMap. All rights reserved.