Re: Derived type argument to subroutine

Gib Bogle <g.bogle@xxxxxxxxxxxxxxxxxxxxxx> wrote:

My question is motivated by concern about performance. I assume that
when I pass a variable that is a derived type as an argument to a
subroutine, is it passed by reference, just as fundamental types are.

1. The standard does not specify that *ANYTHING* is passed by reference.
In practice, they often, but not always are. It is just plain incorrect
to say that "fundamental types are passed by reference". While they
sometimes are, they sometimes aren't. There are even some cases where
they pretty much cannot be.

2. However, that being said, it is just as likely that a derived type
object will be passed by reference. For the most part, the issues simply
don't have much to do with type. It is things orthogonal to type that
are much more important to the question of how arguments are passed. If
anything, to the extent that type matters, I would say that it is the
fundamental types that have greater odds of being passed by something
other than reference.

3. But as you say that your question is motivated by performance issues,
I'd say that you have expressed it in terms that don't really capture
that. Presumably, you don't really care so much about whether it is
passed by reference as whether it has performance comparable to that
expected of pass-by-reference. The answer to that is basically yes.

4. But to reiterate a point made above - a really, really important
point worthy of reiteration - type is *NOT* the most important factor
here. You can get copy-in/copy-out argument passing that can (in some
cases) cause really horrid performance. But the things that typically
trigger that have nothing to do with type. They have much more to do
with array issues and apply to all types.

--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
.

Relevant Pages

  • Re: tagged record child: override constructor?
    ... once that happens there is no going back to the derived type. ... as arguments get them by reference. ... in this inheritance hierarchy may be initialized to refer to an object ... The requirements for view conversion and by-refernce passing ...
    (comp.lang.ada)
  • Re: tagged record child: override constructor?
    ... > that Ada's requirement that tagged types be passed by reference ... > once that happens there is no going back to the derived type. ... A view conversion is still a conversion. ...
    (comp.lang.ada)
  • Re: Derived type argument to subroutine
    ... when I pass a variable that is a derived type as an argument to a subroutine, is it passed by reference, just as fundamental types are. ... But to reiterate a point made above - a really, ...
    (comp.lang.fortran)
  • Re: Derived type argument to subroutine
    ... when I pass a variable that is a derived type as an argument to a subroutine, is it passed by reference, just as fundamental types are. ... is likely to require 3 cache lines. ...
    (comp.lang.fortran)
  • Re: collective nouns -- Re: Optimal programming advice
    ... >>> To drag back in a token Fortran ... >>>reference, if I had a derived type object with multiple components, I ... >>>actually) depend on the derived type rather than on just the components. ...
    (comp.lang.fortran)