Re: Which #define for 32vs64 bit
From: Alex Colvin (alexc_at_TheWorld.com)
Date: 04/28/05
- Next message: Rich Teer: "Re: Why cannot truss peek inside sendmsg()"
- Previous message: recvfrom: "UN*X with non-unique interface names for aliases?"
- In reply to: David Resnick: "Re: Which #define for 32vs64 bit"
- Next in thread: Måns Rullgård: "Re: Which #define for 32vs64 bit"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 28 Apr 2005 21:55:14 +0000 (UTC)
>So what is the solution? The range for line number is 0 to 2147483647,
>at least in C as settable by the #line directive. That could be
>greater than INT_MAX. I guess a cast (ugh) is in order, as in
>(long)__LINE__?
try "%u"?
-- mac the naïf
- Next message: Rich Teer: "Re: Why cannot truss peek inside sendmsg()"
- Previous message: recvfrom: "UN*X with non-unique interface names for aliases?"
- In reply to: David Resnick: "Re: Which #define for 32vs64 bit"
- Next in thread: Måns Rullgård: "Re: Which #define for 32vs64 bit"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|