Re: Program Fails When Parameter Fixed Constants are Changed (F77) ??

"dpb" <none@xxxxxxx> wrote in message news:gskm2k$iod$1@xxxxxxxxxxx

Clearly from the link messages, there are unsatisfied references to the
routine that aren't able to be resolved by the linker. One obvious reason
for this _MIGHT_ be you're not compiling the module which now contains
that routine whereas before it was included in a different source file so
got compiled transparently. A reason for that could be as simple as you
forgot to add the file in your dependency list in a makefile.

What I am cheering for is:

Subroutine DCpZeros()
c *************************************
use DIM
use ABSCISAE
use VVALUES
use DCP
use LST2
use PARM
use maxDIMEN
use CRT
implicit none
.......................
External Dcpval
real Dcpval

If Dcpval is a module procedure the last two lines would
cause a link error. My recommendation: try commenting
them out and see if the error goes away.

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


.

Relevant Pages

  • Re: Program Fails When Parameter Fixed Constants are Changed (F77) ??
    ... simplest combination that mimics the compilation/linker problem. ... One obvious reason for this _MIGHT_ be you're not compiling the module which now contains that routine whereas before it was included in a different source file so got compiled transparently. ... You can place the dummy function in a module but keep it simple--the point is to simply duplicate the outline of the problem to uncover the reason for confusing the linker or why the piece is missing, _not_ to make a working application at this point. ...
    (comp.lang.fortran)
  • Re: get HelpContextIDs or Tags of all userforms
    ... I haven't tried the large routine you recently posted but I had tried the ... >>> For some reason I have to run the Sub twice to get the Form names in ... >> see an obvious reason for any errors at all, ... >> Dim bDebug as boolean ...
    (microsoft.public.excel.programming)
  • Re: Update string too long?
    ... > And we won't question to reason for this routine as you asked... ... Pro SQL Server 2000 Database Design - ... > support the full length of the inserted data? ...
    (microsoft.public.sqlserver.programming)
  • Re: VB6 crashes after writing exe
    ... VB.exe to crash after compiling and writing the exe. ... Code that for some reason has a flaw that the compiler can not digest. ... the exe file. ... best thing to do is look careful at Your code and see where it could be ...
    (microsoft.public.vb.general.discussion)
  • Re: Forth input line buffered, why?
    ... whether interpreting or compiling waits for the user to type ... The main reason is that it's often desirable to manage the input stream while you're in it. ... I have seen implementations that compile a command line before executing it, in order to be able to use things like IF and DO in the command line, but I think executing before the user is finished typing would be very hard to get used to. ...
    (comp.lang.forth)