Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!snorkelwacker.mit.edu!bloom-picayune.mit.edu!news
From: scs@adam.mit.edu (Steve Summit)
Newsgroups: comp.lang.c
Subject: not really Re: Style guides and portability
Message-ID: <1991Jan15.054540.1466@athena.mit.edu>
Date: 15 Jan 91 05:45:40 GMT
References: <1991Jan13.182655.17672@athena.mit.edu> <10608@hydra.Helsinki.FI>
Sender: news@athena.mit.edu (News system)
Reply-To: scs@adam.mit.edu
Organization: Thermal Technologies, Inc.
Lines: 18

In a hastily-added postscript to article
<1991Jan13.182655.17672@athena.mit.edu>, trying
overzealously to prove a point, I wrote:
>P.S. The answer to "How do you print something declared with
>`int32 bigint;' ?" is that you have to abandon printf in favor of
>something you define, like "print32".

In article <10608@hydra.Helsinki.FI>, Lars Wirzenius asks:
>Is there any problem in using 
>	printf("%ld", (long) bigint)
>other than that it's clumsy?

None whatsoever (as long as bigint is known to map to a built-in,
integral type, which in the problem under discussion, it was).
This is a much better solution.  (It's not even all that clumsy.)

                                            Steve Summit
                                            scs@adam.mit.edu