Re: Reference declaration with self-assignment. Is it legal? G++ says it is!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok this is embarrassing... I discovered now that the compiling flags
for all warnings were not active.
Thank you for the help anyway.

Carlos

On 15 May 2015 at 11:55, Marc Glisse <marc.glisse@xxxxxxxx> wrote:
> On Fri, 15 May 2015, Carlos Ferreira wrote:
>
>> Hello to all!
>>
>> I would like to make a quick question.
>>
>> G++ seems to allow this:
>>
>> int& x = x;
>>
>> which creates a null int reference. Why does G++ allows this? Is it a
>> standard thing? This doesn't even generates a warning, and such code can
>> easily cause a segfault.
>
>
> I am actually getting 2 warnings with g++-5 -Wall:
>
> x.c:2:7: warning: reference 'i' is initialized with itself [-Winit-self]
>    int&i=i;
>        ^
> x.c:2:9: warning: 'i' is used uninitialized in this function
> [-Wuninitialized]
>    int&i=i;
>          ^
>
> --
> Marc Glisse



-- 

Carlos Miguel Ferreira
Researcher at Telecommunications Institute
Aveiro - Portugal
Work E-mail - cmf@xxxxxxxx
Skype & GTalk -> carlosmf.pt@xxxxxxxxx
LinkedIn -> http://www.linkedin.com/in/carlosmferreira




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux