The easy solution to this problem is to pass an internal function as
an argument, but of course that is not allowed in standard-conforming
Fortran 90+. What I mean by "internal function" is a function which
is CONTAINed by another function (or subroutine). Now just a little
more specific info so you can feel out the situation.

So what do I want to do?
------------------------------------
Say I want to create a module of integration routines in xy Cartesian
geometry for integrating a user-specified function, f(x,y) over a
polygon. Easy enough.

How do I want to do it?
---------------------------------
I want to use as many integration routines as I can find (e.g. in TOMS/
ACM/textbooks/etc) There is some great stuff out there, written in F77
especially. The difficulty comes in providing a "standardized"
interface to the various integration routines I have collected. I
don't want to go in and rewrite all those routines to accept f(x,y).
I want to write for each method a "wrapper function" of the form
(where ABC specifies some specific method--e.g. trapezoid rule):

An intriguing question :).

I have not worked this out in any detail, but a half-forgotten
feature of FORTRAN 77 is the ENTRY statement. Basically, it defines
a facility that one would now probably use internal functions for,
but it might actually help here.

Something along these lines:

real function integrate_abc( f, n, pg, reltol )
... appropriate declarations

... preparation
call integabc( flocal, ... )
... completion
return

!
! Here it comes
!
entry flocal( pg )

flocal = f(pg)

end function

On 2 sep, 13:53, Arjen Markus wrote:

On Sep 2, 10:01 am, Arjen Markus wrote:

On Mon, 1 Sep 2008 21:02:59 -0700 (PDT), "Will W."
gmail.com> wrote:

This is in the current draft for Fortran 2008. Some compilers (e.g. Intel
Fortran) already support this.

--
Steve Lionel
Developer Products Division
Intel Corporation
Nashua, NH

For email address, replace "invalid" with "com"

On Tue, 2 Sep 2008 04:53:56 -0700 (PDT), Arjen Markus
wrote:

Steve Lionel wrote:

On Sep 2, 10:23 am, Steve Lionel wrote:

GREAT. Do you happen to know as of which version it is supported for
Intel? We have 9.1 on our linux cluster and I would like to be able
to use it there. Thanks,
+W

"Will W." gmail.com> wrote in message
news:563f03fb-e1a2-4151-9686-b47b50fb39fb@56g2000hsm.googlegroups.com...

Since approximately DVF.

Dick Hendrickson att.net> wrote:

...

Entry has a large number of "quirks" and special cases. At one time it
was on a list of features to be declared obsolescent. I don't recall
whether that survived the development process to date, but in any case,
I would not personally recommend using ENTRY for anything in new code. A
module provides a better way of doing most of this style of thing (where
two procedures share some of the same data).