JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for COMP-FORTRAN-90 Archives


COMP-FORTRAN-90 Archives

COMP-FORTRAN-90 Archives


COMP-FORTRAN-90@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

COMP-FORTRAN-90 Home

COMP-FORTRAN-90 Home

COMP-FORTRAN-90  1998

COMP-FORTRAN-90 1998

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: How can I do it on f90?

From:

[log in to unmask]

Reply-To:

[log in to unmask]

Date:

Tue, 14 Jul 1998 10:09:19 +0200 (MET DST)

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (185 lines)

David Leal Valmana <[log in to unmask]> wrote:
[...]
> I my case I use the following compilation:
> f90 -c optimization.f90
> f90 -c specific_funcions.f90
> f90 -o test_prob test_prob.f90 optimization.o specific_funcions.o

Since optimization_mod is using specific_function_mod, most (all?)
compilers will need to see specific_funcions.f90 first in order to
create the module information neccessary for the compilation of
optimization.f90.

> where
> optimization and speficif_functions are the file containing the modules
> optimization_mod and specific_function_mod respectively.
> 
> So if I want to solve only one problem is inmidiatly, but what about to
> solve a lot of test problem in the same way?
> 
> prob_1 : specific_function1_mod 
> prob_2 : specific_function2_mod
> prob_3 : specific_function3_mod
> .
> .
> .
> prob_n :specific_functionn_mod
> 
> 
> Because We have to place the USE statement only at the begining of the
> program is not posible to use a kind of bucle for loading each time the
> specific module for each problem.
> 
> Has someone any idea about how to solve this case?

As you point out, you can't use fortran modules like variables or
arguments, their relations are run time invariant. However, this does
not apply to their content. So you can use procedure parameters in
order to feed your optimization algorithms with various functions.

I would do it similar to this example:

  MODULE definitions_mod
    IMPLICIT NONE
    ! Put things that are needed for the definition of your
    ! specific functions in here. Like kind parameters, derived
    ! types, etc..

    INTEGER, PARAMETER:: sp = SELECTED_REAL_KIND(6)

  END MODULE definitions_mod


  MODULE specific_functions_mod
    USE definitions_mod
    ! This module is used by the main program but not by the
    ! optimization module. It may as well be splitted into
    ! several modules, if you like.

    IMPLICIT NONE

  CONTAINS

    FUNCTION specfun1(x)
      REAL(sp), INTENT(IN):: x
      REAL(sp)            :: specfun1

      [...]

    END FUNCTION specfun1

    FUNCTION specfun2(x)
      REAL(sp), INTENT(IN):: x
      REAL(sp)            :: specfun2

      [...]

    END FUNCTION specfun2

  END MODULE specific_functions_mod


  MODULE optimization_mod
    USE definitions_mod  ! This use is for the declaration of function
                         ! optimize itself. It is invisible to the
                         ! interface below...
    IMPLICIT NONE

  CONTAINS

    FUNCTION optimize(f, ...)
      INTERFACE
         FUNCTION f(x)
           USE definitions_mod ! ... therefore it has to be used here again.
           REAL(sp), INTENT(IN):: x
           REAL(sp)            :: f
         END FUNCTION f
      END INTERFACE
      REAL(sp):: optimize

      [...]

    END FUNCTION optimize

  END MODULE optimization_mod


  PROGRAM test_prob
    USE definitions_mod
    USE specific_functions_mod
    USE optimization_mod
    IMPLICIT NONE

    WRITE(*, *) optimize(specfun1, ...)
    WRITE(*, *) optimize(specfun2, ...)

  END PROGRAM test_prob


If you want to split specific_functions_mod into separate modules for
each function and don't want to care about choosing distinct names for
functions and other entities across these modules, you can use local
renaming in the main program:


  MODULE specific_function1_mod
    USE definitions_mod
    IMPLICIT NONE

  CONTAINS

    FUNCTION specfun(x)
      REAL(sp), INTENT(IN):: x
      REAL(sp)            :: specfun

      specfun = 1 + x

    END FUNCTION specfun

  END MODULE specific_function1_mod


  MODULE specific_function2_mod
    USE definitions_mod
    IMPLICIT NONE

  CONTAINS

    FUNCTION specfun(x)
      REAL(sp), INTENT(IN):: x
      REAL(sp)            :: specfun

      specfun = 1 + x + x ** 2

    END FUNCTION specfun

  END MODULE specific_function2_mod


  PROGRAM test_prob
    USE definitions_mod
    USE specific_function1_mod, ONLY: specfun1 => specfun
    USE specific_function2_mod, ONLY: specfun2 => specfun
    USE optimization_mod
    IMPLICIT NONE

    WRITE(*, *) optimize(specfun1)
    WRITE(*, *) optimize(specfun2)

  END PROGRAM test_prob


Hope this helps
Michael
-- 
*****************************************************************************
Michael Steffens                     Institut f. Meteorologie u. Klimatologie
Tel.: +49-511-7624413                                   Universitaet Hannover
email: [log in to unmask]         Herrenhaeuser Str. 2
       [log in to unmask]                          D-30419 Hannover

    PGP fingerprint = FA BE 6C 1C F6 C3 EC 33  DD 42 6B 7F DE CF 84 B8


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
February 2023
November 2022
September 2022
February 2022
January 2022
June 2021
November 2020
September 2020
June 2020
May 2020
April 2020
December 2019
October 2019
September 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
April 2015
March 2015
January 2015
December 2014
November 2014
October 2014
August 2014
July 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
July 2013
June 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
August 2010
July 2010
June 2010
March 2010
February 2010
January 2010
December 2009
October 2009
August 2009
July 2009
June 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager