Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!bu.edu!buphy!shank
From: shank@buphy.BU.EDU (Jim Shank)
Newsgroups: comp.lang.fortran
Subject: Re: archiving block data subroutines...
Message-ID: <69366@bu.edu.bu.edu>
Date: 26 Nov 90 19:59:54 GMT
References: <BURLEY.90Oct23041048@world.std.com> <1990Nov22.074157.15813@agate.berkeley.edu> <7388@hub.ucsb.edu>
Sender: news@bu.edu.bu.edu
Organization: Physics Department, Boston University
Lines: 37


In article <1990Nov22.074157.15813@agate.berkeley.edu> jerry@violet.berkeley.edu (Jerry Berkman) writes:

>>...
>>There is probably no easy way which works on all systems to get block data's
>>to load.  Some UNIX systems will load a block data in a library if it is in
>>the same source file as another program segment being loaded, some UNIX systems
>>will not.  All the non-UNIX systems I have used would not.
>>	- Jerry Berkman, U.C. Berkeley, jerry@violet.berkeley.edu

>I agree that there is no universal solution.  Just for the heck of it,
>here is yet another way to violate the standard:

>C    <Never call this routine!  Just leave it near your main.
>      SUBROUTINE KABOOM
>      CALL BD
>      END
>C    <This BD is no subroutine.  It's the block data.  Tee hee.
>C    <Hope this will fool the loader.

I always thought the way to do this was to declare the Block Data
subprogram EXTERNAL in the main routine:


        PROGRAM MAIN


        EXTERNAL BLKDAT


        . 
        .
        .
        STOP

This forces the linker to include the Block data subprogram.