Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject: Re: Python 3 is killing Python
Date: Thu, 07 Aug 2014 21:07:40 -0400
Organization: IISS Elusive Unicorn
References: <mailman.10416.1401304999.18130.python-list@python.org> <7xha49wumw.fsf@ruckus.brouhaha.com> <CACwCsY5TTkgH1KNdToXd527weJBNxq_rTBwWvtKV-ngB6iUoaA@mail.gmail.com> <mailman.10427.1401316716.18130.python-list@python.org> <88649f2d-76c2-41af-a509-23486bd06dff@googlegroups.com> <53e2f47a$0$6512$c3e8da3$5496439d@news.astraweb.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.12731.1407460120.18130.python-list@python.org>
Lines: 50
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:75858

On Thu, 07 Aug 2014 13:37:29 +1000, Steven D'Aprano
<steve+comp.lang.python@pearwood.info> declaimed the following:

>beliavsky@aol.com wrote:
>
>> Fortran compiler vendors such as Intel, IBM, Oracle/SUN and open source
>> projects such as gfortran are updating their compilers to the Fortran 2003
>> and 2008 standards while also keeping the ability to compile all the old
>> Fortran code. FORTRAN 77 programmers and programs will not be forced to
>> move to modern Fortran, 
>
>How about FORTRAN IV and FORTRAN 66 users? Where's their support? Why aren't
>they moaning and gnashing their teeth that they're so cruelly and
>unreasonably forced to upgrade?
>
	Most likely, the formal standard document for Fortran still mandates
F77 compatibility -- yet most likely also lists those F77 features which
are deprecated/obsolete and may go away in the next standard. Just as F77
standard listed F-IV features that would be going away in the future.

	Also, being a fully compiled/static language, the compiler can probably
spend the needed time to determine the dialect being used for some
constructs. Python's run-time dynamics may preclude doing that.

	Third -- said compatibility may still require using a compile-time flag
to indicate dialect for some features.

	Heck, at one time the "FORTRAN standard" actually defined two levels of
the language, and the subset level could not compile stuff that was legal
in the full language level. Things like computed arguments in a subprogram
call:

	call xyz(i-1, i, i+1)

could be valid or invalid depending upon which level of the single standard
the compiler followed. I once was involved in an effort that ported an
application in "full" FORTRAN to a machine with the subset level. You
wouldn't believe the number of

inxs, inks, jinx, jynx, jinks, linx, lynx, lyncs etc. junk variables had to
be created:

	jinx = i-1
	lynx = i+1
	call xyz(jinx, i, lynx)

-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/