From: "Steve Dondley" <stevedondley@attbi.com>
To: <gcc-help@gcc.gnu.org>
Subject: RE: Avoiding "assignment from incompatible pointer type" warning
Date: Sun, 13 Oct 2002 09:34:00 -0000 [thread overview]
Message-ID: <FAECKOGIHAIBBPKBOKGNOEDNDOAA.stevedondley@attbi.com> (raw)
In-Reply-To: <000d01c272d5$85368b20$0100a8c0@windows9q3yn19>
Ah, OK. When I tried casting earlier, I was putting the cast on the lvalue.
I don't have the world's sharpest tech mind but with persistence I'll get it
eventually.
> -----Original Message-----
> From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org]On
> Behalf Of Joshua Nye
> Sent: Sunday, October 13, 2002 12:28 PM
> To: Steve Dondley; gcc-help@gcc.gnu.org
> Subject: Re: Avoiding "assignment from incompatible pointer type"
> warning
>
>
> Hi Steve,
>
> What you're looking for is a cast. i.e.:
>
> int *p;
> float g = 3.141592653589793238;
> p = (int *)&g;
>
> --josh
>
> ----- Original Message -----
> From: "Steve Dondley" <s@dondley.com>
> To: <gcc-help@gcc.gnu.org>
> Sent: Sunday, October 13, 2002 12:13 PM
> Subject: Avoiding "assignment from incompatible pointer type" warning
>
>
> > Hi,
> >
> > I've written a simple program that print out each bit of a
> floating point
> > variable so I can learn how floating point numbers are represented in
> > memory. The program contains the following statements:
> >
> > int *p;
> > float g = 2.0625;
> > p = &g;
> >
> > The third statement above generates an "assignment from incompatible
> pointer
> > type" warning for obvious reasons. Other than this, the
> program compiles
> > fine and works.
> >
> > My question is: Is there a way to properly assign a pointer of one type
> to
> > a variable of different type so that the warning is suppressed?
> >
> > Thanks again.
> >
> >
>
>
>
next prev parent reply other threads:[~2002-10-13 16:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 9:08 Steve Dondley
2002-10-13 9:28 ` Joshua Nye
2002-10-13 9:34 ` Steve Dondley [this message]
2002-10-13 15:09 ` Florian Weimer
2002-10-13 15:19 ` Joshua Nye
2002-10-15 11:24 ` Joshua Nye
2002-10-21 3:12 ` Florian Weimer
2002-10-21 4:22 ` Claudio Bley
2002-10-21 4:30 ` Florian Weimer
2002-10-21 6:48 ` Claudio Bley
2002-10-21 4:42 ` Sebastian Huber
2002-10-21 6:43 ` John Love-Jensen
2002-10-21 6:52 ` Florian Weimer
2002-10-13 13:37 Moore, Mathew L
2002-10-13 15:10 ` Florian Weimer
2002-10-21 6:07 Moore, Mathew L
2002-10-21 7:04 Moore, Mathew L
2002-10-21 7:17 ` Florian Weimer
2002-10-21 7:43 ` John Love-Jensen
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=FAECKOGIHAIBBPKBOKGNOEDNDOAA.stevedondley@attbi.com \
--to=stevedondley@attbi.com \
--cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).