Re: A question on string literals

Richard Heathfield wrote:
>
> pete wrote:
>
> > Richard Heathfield wrote:
> >>
> >> Chris Barts wrote:
> >>
> >> > In article <1123579479.194294.182390@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
> >> > Sriram Rajagopalan wrote:
> >> >>
> >> >> char arr1[] = { "Hello" };
> >> >> arr1 = 0; // Not allowed.
> >>
> >> Correct.
> >>
> >> >
> >> > No, that is still allowed: The array 'decomposes' into a pointer
> >>
> >> Incorrect. Such decay happens only in value contexts,

Where are you getting that from?

--
pete
.

Relevant Pages

  • Re: How to be a good programmer?
    ... pete wrote: ... > Richard Heathfield wrote: ... >>An interesting resource. ... I followed the C source link and ...
    (comp.programming)
  • Re: A question on string literals
    ... >> pete wrote: ... I must admit I was getting it from Chris Torek's constant incantations ... Richard Heathfield ... mail: rjh at above domain ...
    (comp.lang.c)
  • Re: C FAQ wiki
    ... Richard Heathfield wrote: ... > pete wrote: ... converted 'The Last Supper' to ascii art already knows that the third ... from the left is a dead ringer for Dennis Ritchie... ...
    (comp.lang.c)
  • Re: Mystery: static variables & performance
    ... "pete" wrote in message ... > Richard Heathfield wrote: ... >> least get some feedback as to what is wrong with his correction. ...
    (comp.lang.c)
  • undefined vs. not covered by the standard, was Re: Theodore Adorno
    ... pete wrote: ... > Richard Heathfield wrote: ... Followup set to comp.std.c ... When your code invokes ...
    (comp.programming)