linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Kiehl <Holger.Kiehl@dwd.de>
To: Jeff Woods <Kazrak+kernel@cesmail.net>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Unsigned off_t?
Date: Mon, 25 Jul 2005 09:00:28 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0507250858480.3913@praktifix.dwd.de> (raw)
In-Reply-To: <6.2.3.4.0.20050725025009.042ad5f0@no.incoming.mail>

On Mon, 25 Jul 2005, Jeff Woods wrote:

> At 7/25/2005 08:47 +0000, Holger Kiehl wrote:
>> I would like to have an unsigned off_t, what is the best and portable way 
>> to define this? Currently I use the following code:
>> 
>>    #if SIZEOF_OFF_T == 4
>>    typedef unsigned long       u_off_t;
>>    #else
>>    typedef unsigned long long  u_off_t;
>>    #endif
>> 
>> SIZEOF_OFF_T is returned from the gnu autoconfig tools.
>> 
>> Is this the correct way of doing this? Or is there some better more 
>> portable way?
>
> Does the following do what you want?
>
>        typedef unsigned off_t u_off_t;
>
No, this is what I tried first but does not compile. Try the following code:

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

    typedef unsigned off_t u_off_t;

    int
    main(void)
    {
       u_off_t a;

       return 0;
    }

Thanks,
Holger


  reply	other threads:[~2005-07-25  9:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25  8:47 Unsigned off_t? Holger Kiehl
2005-07-25  8:53 ` Jeff Woods
2005-07-25  9:00   ` Holger Kiehl [this message]
2005-07-26  5:24 ` Glynn Clements
2005-07-26  7:38   ` Holger Kiehl
2005-07-26 16:53     ` superblock & inode's Nanakos Chrysostomos
2005-07-26 16:59       ` Robert P. J. Day
2005-07-27  5:21       ` sumit kalra
2005-07-27  7:24       ` Glynn Clements
2005-07-27 18:53         ` Nanakos Chrysostomos
2005-07-27  7:23     ` Unsigned off_t? Glynn Clements
2005-07-27 20:09       ` Holger Kiehl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.61.0507250858480.3913@praktifix.dwd.de \
    --to=holger.kiehl@dwd.de \
    --cc=Kazrak+kernel@cesmail.net \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).