Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Tim Chase <python.list@tim.thechases.com>
Newsgroups: comp.lang.python
Subject: Re: Considering migrating to Python from Visual Basic 6 for engineering applications
Date: Sun, 21 Feb 2016 12:19:06 -0600
Lines: 52
Message-ID: <mailman.20.1456079311.20994.python-list@python.org>
References: <90cc50d2-1ce5-4588-9bfd-a49d439f00dd@googlegroups.com> <mailman.226.1455748107.22075.python-list@python.org> <14c75a68-0d2e-45cc-8d73-0d71b6a6aea6@googlegroups.com> <mailman.243.1455790578.22075.python-list@python.org> <c977991d-a635-4a8f-a0e3-28f436b378f6@googlegroups.com> <CAPTjJmqF2TciSgr=qdyy+9WcWrhYVvo7VCk6s5aOo0t38PpgTw@mail.gmail.com> <mailman.5.1455808876.2289.python-list@python.org> <f136cf1a-b332-485f-889a-ef701ca5993c@googlegroups.com> <mailman.20.1455823868.2289.python-list@python.org> <9e57761f-26e1-41c5-8e71-23800de1fdd3@googlegroups.com> <mailman.48.1455890911.2289.python-list@python.org> <7f9c473e-b0c2-4d77-91d1-d0733c93b12d@googlegroups.com> <pYydnYLkXtvuh1XLnZ2dnUU7-SGdnZ2d@giganews.com> <23d8156f-1808-4395-9c04-27d2984fe67c@googlegroups.com> <xtadnfpDuOib-lTLnZ2dnUU7-fednZ2d@giganews.com> <nacd55$5sp$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
In-Reply-To: <nacd55$5sp$1@dont-email.me>
Precedence: list
Xref: csiph.com comp.lang.python:103313

On 2016-02-21 13:16, BartC wrote:
> > No need for anyone to re-invent the
> > wheel!  ;-)
> 
> I keep seeing this in the thread. Python has all this capability,
> yet it still requires a lot of fiddly code to be added to get
> anywhere near as simple as this:
> 
>    read f, a, b, c
> 
> And this is code that is not going to be obvious to anyone starting
> out. Even accepting that syntax limitations might require this to
> be written as:
> 
>    readline(f, a, b, c)

Well, if you know what the line is going to contain, that can be
written as

  a, b, c = f.readline().split()

> I can't see a straightforward way of making this possible while
> still keeping a, b and c simple integer, float or string types
> (because Python's reference parameters don't work quite the right
> way).

However, that does give you byte-strings since that's what comes out
of files.  If you know they're ints, you can force that:

  a, b, c = map(int, f.readline().split())

> (There is also the question of 'readline' knowing what types of
> values to read. This information would not be needed in Fortran or
> Basic but somehow needs to be supplied here, if a particular set of
> types is to imposed on the input.)
> 
> In other words, it seems this particular wheel does require
> re-inventing!

In both Fortran & BASIC, you specify that information somewhere as
well.  However, it sounds like you define those at the
variable-definition level (it's been over a decade since I done any
BASIC and far longer since I've even touched any Fortran, so forgive
me if I'm a tad rusty) instead of where its read from the file.

-tkc