Re: Who uses clapack?

From: Everett M. Greene (mojaveg_at_mojaveg.iwvisp.com)
Date: 12/18/04 

Date: Sat, 18 Dec 2004 10:19:51 PST

Dan Nagle <dannagle@verizon.net> writes:
> mojaveg@mojaveg.iwvisp.com (Everett M. Greene) wrote:
> >Dan Nagle <dannagle@verizon.net> writes:
>
> <snip requoted>

> >> Fortran 2003 was officially released in November,
> >> and the Fortran committees are full speed ahead
> >> working on Fortran 2008.
> >
> >Churning out revised standards that often borders on the
> >irresponsible (unless one is looking out for the employment
> >opportunities of Fortran compiler developers).
>
> Tell ISO to change their rules.
>
> We alternate between "Major" and "Minor" revisions,
> f08 will be a minor revision. We also must certify
> a particular standard to be continued every five years,
> so unused standards are automatically withdrawn.
> Again, it's an ISO rule.
>
> BTW, C++ had a revision in 2003, too (IIRC).
> I believe C has no plans for future revisions,
> they are in maintenance mode, at least for now,
> at least as far as normative text is concerned.

I recall ANSI X3J sending a letter to all its committees
around 1980 about the five-year rule. The committe with
which I was involved at the time sent back a letter
saying that the five-year cycle was impractical for a
programming language standard and something of the order
of ten years would be more reasonable. I don't recall
the committee ever getting any more correspondence on the
subject.

At least one of the X3J committees does a pro-forma
reaffirmation at the five year intervals of a ten-year
cycle on revisions. Errata corrections and interpretations
can be issued as needed.

Relevant Pages

  • Re: C++ and Middleware
    ... C++/CLI is largely a Microsoft initiative and is being standardised by ... a committee within ECMA, not the ISO and ANSI committees ... that produce C++ standards (JTC1/SC22/WG21 and INCITS J16 ... Some members of the latter committees have been able ...
    (comp.lang.cpp)
  • Re: Whats wrong with GEDCOM ?
    ... The standards designed/specified by big committees full of big-wig vendors ... Smaller, more focused, committees tend to define cleaner standards. ... design-by-committee approach. ...
    (soc.genealogy.computing)
  • Re: [9fans] Brdline
    ... standards czar, your brilliant expert, with a background in law and social science as well as technology, who is able to apply duly constituted public authority to a standard. ... My last employer killed my sense of worth by pilling me on standards committees, evaluation committees, coffee-cup-washing committees ad infinitum. ... I may not be a brilliant expert, but they put me there as an expert, and killed the expertise simultaneously. ...
    (comp.os.plan9)
  • Re: A question about graphic I/O
    ... Is it the reluctance of vendors who sit at standards ... >committees and have competing products? ... the errors themselves, i.e., the goofs that we Fortran users are ... We can make errors on any platform. ...
    (comp.lang.fortran)
  • The Latest ISO 17799 and ISO 27001 Newsletter Published
    ... plus commentary on recent Information Security ... ISO 17799/27001 Toolkit Versions ... the support toolkit for the standards. ... The long awaited standard for business continuity, ...
    (comp.security.misc)