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: IO buffer overflow

From:

Richard E Maine <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Wed, 24 Nov 2004 13:03:28 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (58 lines)

On Nov 24, 2004, at 12:06 PM, Van Snyder wrote:

> Of course, it was an extension.  Being so, X3J3 never standardized it,
> perhaps because of the resistance to standardizing existing practice.

That hyperbole seems a bit, harsh.  Close to the point of being flame
bait.

In well over a decade on J3, I never once heard even a hint of a single
member suggesting that being existing practice was a reason not to
standardize something.  I don't think it was because my ears were
closed.

I have certainly heard plenty of arguments that being existing practice
was not in itself always sufficient reason to standardize something.
But that statement is very different.  In fact, it is opposite in sign.
One statement argues that existing practice is a negative. The other
acknowledges it as a positive, but not necessarily sufficiently
positive to outweigh other negatives.  There are always negatives to
every proposal. If nothing else, every proposal requires dome work,
which is a negative. Might not be a big negative, and how big is often
debatable, but the sign is obvious enough.

Sometimes the positive of existing practice has been strong enough to
overcome substantial negatives.  For example, to my knowledge, existing
practice is the main reason that the bit intrinsics look quite like
they do. I seriously doubt that they would have had quite the same
syntax if it were not for the weight of existing practice.

There have been cases where multiple existing practices were
inconsistent on details. In several such cases, the standard did avoid
conflicting with either of the old ones. But that is done specifically
to *SUPPORT* existing practice by continuing to allow it as an
alternative extension form, rather than by dictating one choice that
would invalidate existing codes using one of the incompatible existing
practices. I've been involved in a few of those.  (Command-line
arguments come to mind).

Of course I've seen a lot of proposals to standardize some existing
feature from some compiler.  Many of those proposals got rejected.
Many proposals of all kinds get rejected (there being orders of
magnitude more proposals than are practical to do, and some proposals
directly conflicting with others).  But never once has the fact that it
was existing practice been even hinted at as a reason for rejection.
Yes, I'm including internal committee discussions, and even private
ones over dinner, so no, I don't buy any theory that involves that as
being the real reason behind the scene.

But all in all, what I've seen most of along these lines is people
whose proposals got rejected making up what I can only categorize as
conspiracy theories to explain the rejection. The hypothesized basis of
the conspiracy varies, prejudice against existing practice being one.

--
Richard Maine                |  Good judgment comes from experience;
[log in to unmask]       |  experience comes from bad judgment.
                             |        -- Mark Twain

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