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  2004

COMP-FORTRAN-90 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: configurable default real

From:

Alvaro Fernandez <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Mon, 8 Mar 2004 17:41:43 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (49 lines)

No, I caught the INCLUDE file. I was more replying to Richard Maine, who was
answering my question by explaining compile-time polymorphism. Once I saw
that INCLUDE was being used, I understood how Van Snyder was doing his
approach. My point had been there was no way to do this with just interfaces
and modules. INCLUDE completes the picture, providing something like a
preprocessor. (I caught the ? tokens).

Alvaro


-----Original Message-----
From: Fortran 90 List [mailto:[log in to unmask]] On Behalf Of
[log in to unmask]
Sent: Monday, March 08, 2004 5:18 PM
To: [log in to unmask]
Subject: Re: configurable default real

> I'm sorry, but that's not what I mean... Clearly, you can have two
> functions/routines, put them in an interface block directly or through the
> MODULE PROCEDURE statement, and have the compiler pick among them by
> "disambiguating" based upon the kinds of the arguments being passed in and
> the kinds of the dummy arguments waiting to receive them in the procedure.
> The compiler swaps the generic name sin() for sin_single_precision, and
away
> we go - compile-time polymorphism.
>
> But what Van Snyder said was that he had a _single version_ which he wrote
> for all kinds and selected internally. That's at least what I understood.

I think Alvaro missed one critical point.  My "single version" is in an
include file, with declarations that depend on a kind type parameter that is
set before the include.  This lets me write the procedure body once; the
processor compiles it twice -- once with kind(0.0e0), once with kind(0.0d0).
Of course, the whole procedure isn't in the include file.  I put the
procedure header and the declaration of the kind type parameter in the
module -- once for single, once for double -- and everything else in the
include file.  This is about the best I can do with Fortran 95, as far as
not duplicating effort.  Sometimes, I can't even do that well.  For example,
for my sort routine, to create one for two kinds of real and one kind of
integer, I have to declare some dummy arguments, and several local
variables,
before the include.

--
Van Snyder                    |  What fraction of Americans believe
[log in to unmask]       |  Wrestling is real and NASA is fake?
Any alleged opinions are my own and have not been approved or disapproved
by JPL, CalTech, NASA, Sean O'Keefe, George Bush, the Pope, or anybody else.

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