This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Change to lvalue casting in gcc v4.01
- From: corey taylor <corey dot taylor at gmail dot com>
- To: "kenkahn at optonline dot net" <kenkahn at optonline dot net>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Tue, 13 Sep 2005 10:10:31 -0500
- Subject: Re: Change to lvalue casting in gcc v4.01
- References: <4325F435.1080704@optonline.net> <BF4C4CC6.17D7%eljay@adobe.com> <df8db5fefcd.4326b27d@optonline.net>
- Reply-to: corey dot taylor at gmail dot com
Kenkahn,
Starting with 3.4 these are the rules for C++ and C:
http://gcc.gnu.org/gcc-3.4/changes.html
I do not know if the deprecation in C was removed in 4.0
corey
On 9/13/05, kenkahn@optonline.net <kenkahn@optonline.net> wrote:
> >> char *buffer[1024];
> >> *((uint32_t)buffer) = 0x1234;
> >
> >I don't believe that has ever been valid.
>
> *SIGH* I meant to write
>
> char buffer[1024];
> *((uint32_t)buffer) = 0x1234;
>
> Is that better (and allowed)?
>