Re: It Hurts When I Do This off topic

"Dick Hendrickson" <dick.hendrickson@[EMAIL PROTECTED]
> wrote in message 
news:NX7Oj.210915$cQ1.165669@[EMAIL PROTECTED]
>>>>
http://softwareblogs.intel.com/2008/03/31/doctor-it-hurts-when-i-do-t...

> In it Steve said
> "Still, most of the time, the (:) is "harmless" in that it does not
> change the overall meaning of the program, since an array section is
> "definable" (can be stored into), as long as you don't use a vector
> subscript such as A([1,3,5,7])."

> That particular example is perfectly definable.  It's only many
> to one assignments that are prohibited.  Steve undoubtedly meant
> A([1,3,5,3]). ;)

Well, sort of.  If A is of a user-defined type, defined assignment
can't work for array sections with vector subscripts because it
would require a dummy argument to be definable which it can't be in
this case from the the paragraph of section 12.4.1.3 of N1601.pdf.

Curiously, ifort implements this correctly as an extension (IIRC)
but fails when the expr of a defined assignment is an array section
with a vector subscript even though the latter case is actually
conforming.

What should a compiler do when the variable in a defined assignment
is an array section with a vector subscript?  Should it call the
elemental subroutine anyhow, with the result that nothing gets
copied out to the variable, or recognize this case and use derived-
type intrinsic assignment instead?

-- 
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end