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  2000

COMP-FORTRAN-90 2000

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: OO (C++) emulation in F95 ...

From:

Tom Clune <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 2 May 2000 14:24:29 -0400 (EDT)

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (74 lines)


I guess that I should not have read the draft while trying
to fall asleep.  (I did much better at the latter.)

OK, So F2K probably has everything that we need, but 5 years
too late for practical purposes.   If we go the route of the
preprocessor, I'll definitely push for making the client code
look as much like F2K code as possible.   I'll leave it up to
others around here as to whether the class specifications should 
look more like fortran or C++.   As you say, the preprocessor
(or its cousin) should be able to spit out pure F2K code
for later on.  I feel that such an extension will be relatively
trivial by the time one extracts and parses the information
contained is a class declaration.

Cheers,

- Tom


>>>>> "Van" == Van Snyder <[log in to unmask]> writes:

    Tom.Clune> ...  my guess is that it [Perl] would be a more
    Tom.Clune> suitable language for the preprocessor than fortran per
    Tom.Clune> se.  Another responder suggested using m4.

    Van> I give students in my compiler classes a
    Van> compiler-construction framework written in Pascal, Modula-2,
    Van> Ada 95 or Fortran 90.  The ones in Ada and Fortran 90 are
    Van> tied, in my opinion, for cleanliness.  If you write the
    Van> preprocessor using ad hoc search-and-replace methods instead
    Van> of using the usual systematic compiler construction methods,
    Van> Perl or m4 might be more appropriate.  William Clodius has a
    Van> parser for Fortran 90 at
    Van> http://hometown.aol.com/wclodius/index.html.  There's also a
    Van> more substantial front-end at
    Van> http://ftp.digital.com/pub/plan/eli/Examples/.

    Tom.Clune> ...  Do "extended" objects inherit methods from the
    Tom.Clune> parent object, or just the components?

    Van> The current F2K design inherits "methods."  They're called
    Van> "type-bound procedures" in the draft.

    Tom.Clune> ... by the time I implement a preprocessor of this
    Tom.Clune> power, converting it to accept a different syntax (F2K
    Tom.Clune> <-> C++) will be relatively easy....

    Van> I hope you're also planning to make a preprocessor that will
    Van> accept the old syntax as input, and emit the new syntax
    Van> (perhaps pure F2k) as output.  Or would you rather ask your
    Van> clients either to throw away their "legacy" code or re-write
    Van> it?

    Van> -- What fraction of Americans believe | Van Snyder Wrestling
    Van> is real and NASA is fake?  | [log in to unmask] Any
    Van> alleged opinions are my own and have not been approved or
    Van> disapproved by JPL, CalTech, NASA, Dan Goldin, Bill Clinton,
    Van> the Pope, or anybody else.



--

-- 
Thomas Clune, Ph.D.	Parallel Applications Consultant
SGI			[log in to unmask]          
Code 931 NASA GSFC      301-286-4635 (work)
Greenbelt, MD 20771	301-286-1634 (fax)



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

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