Re: strange linking problem

In article <D8ydneYJcsMupOzfRVn-qw@xxxxxxxxxxx>,
glen herrmannsfeldt <gah@xxxxxxxxxxxxxxxx> wrote:

> This can cause some interesting
> effects if you accidentally (or not) name COMMON the same as a
> subroutine.

Been there. Was no fun. :-( Accidentally.

--
Richard Maine | Good judgment comes from experience;
email: my first.last at org.domain | experience comes from bad judgment.
org: nasa, domain: gov | -- Mark Twain
.

Relevant Pages

  • Re: Multiple Values within Multi-Value Fields...
    ... but common variables are initialized to 0 when the common is ... 001 SUBROUTINE HELLO ... Prev by Date: ...
    (comp.databases.pick)
  • Re: Multiple Values within Multi-Value Fields...
    ... but common variables are initialized to 0 when the common is ... 001 SUBROUTINE HELLO ... Prev by Date: ...
    (comp.databases.pick)
  • Re: fortran95 error
    ... At a guess you are using a subroutine like: ... declarations I saw nothing that should have given the above error. ... or better yet in a separate COMMON of their own. ... they are all default reals. ...
    (comp.lang.fortran)
  • Re: fortran95 error
    ... At a guess you are using a subroutine like: ... declarations I saw nothing that should have given the above error. ... or better yet in a separate COMMON of their own. ... they are all default reals. ...
    (comp.lang.fortran)
  • Re: reading two separate files
    ... in the first file? ... If you want to read different files using the same subroutine there ... common /a1b1/ a,b,c ...
    (comp.lang.fortran)