public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Koning <paulkoning@comcast.net>
To: David Malcolm <dmalcolm@redhat.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: [RFC] Adding Python as a possible language and it's usage
Date: Wed, 18 Jul 2018 00:38:00 -0000	[thread overview]
Message-ID: <F0F29197-FEE7-49D7-B936-79878C441CD1@comcast.net> (raw)
In-Reply-To: <1531873416.18413.81.camel@redhat.com>



> On Jul 17, 2018, at 8:23 PM, David Malcolm <dmalcolm@redhat.com> wrote:
> 
>>> Hi.
>>> 
>>> I've recently touched AWK option generate machinery and it's quite
>>> unpleasant to make any adjustments. My question is simple: can we
>>> starting using a scripting language like Python and replace usage
>>> of
>>> the AWK scripts? It's probably question for Steering committee, but
>>> I
>>> would like to see feedback from community....
>>> I'm looking forward to a feedback.
>>> Martin

David gave a number of good arguments.  I support Martin's proposal, both as to replacing AWK and specifically the choice of Python for that purpose.

Python fits the bill very well in my experience.  I've used it to write several large programs, including such non-obvious ones as two network protocol stack implementations.

In roughly 40 years, and roughly 40 programming languages, I've only twice encountered a language where I could go from knowing nothing at all to writing a substantial real world program in just one week: Pascal (in college) and Python (about 15 years ago).  This is why Python became my language of choice whenever I don't need the speed or small memory footprint of C/C++.

	paul


  reply	other threads:[~2018-07-18  0:38 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 20:37 David Niklas
2018-07-18  0:23 ` David Malcolm
2018-07-18  0:38   ` Paul Koning [this message]
2018-07-18 16:41   ` doark
2018-07-18 17:22     ` doark
     [not found] <1531832440.64499.ezmlm@gcc.gnu.org>
2018-07-17 17:13 ` Basile Starynkevitch
2018-07-17 23:52   ` David Malcolm
  -- strict thread matches above, loose matches on Subject: below --
2018-07-17 12:49 Martin Liška
2018-07-18  1:01 ` David Malcolm
2018-07-19 20:24   ` Karsten Merker
2018-07-20 10:02     ` Matthias Klose
2018-07-20 10:07     ` Martin Liška
2018-07-18  9:51 ` Richard Biener
2018-07-18 10:03   ` Richard Earnshaw (lists)
2018-07-18 10:56   ` David Malcolm
2018-07-18 11:08     ` Jakub Jelinek
2018-07-18 11:31     ` Jonathan Wakely
2018-07-18 12:06       ` Eric S. Raymond
2018-07-18 12:15         ` Jonathan Wakely
2018-07-18 12:50           ` Joel Sherrill
2018-07-18 14:29             ` Matthias Klose
2018-07-18 14:46               ` Janne Blomqvist
2018-07-20 10:01               ` Martin Liška
2018-07-20 16:54                 ` Segher Boessenkool
2018-07-20 17:12                   ` Paul Koning
2018-07-20 17:59                     ` Segher Boessenkool
2018-07-20 18:59                       ` Konovalov, Vadim
2018-07-20 20:09                         ` Matthias Klose
2018-07-20 20:15                           ` Konovalov, Vadim
2018-07-18 21:28           ` Eric S. Raymond
2018-07-23 14:31     ` Joseph Myers
2018-07-18 22:42   ` Segher Boessenkool
2018-07-19 12:28     ` Florian Weimer
2018-07-19 20:08       ` Richard Earnshaw (lists)
2018-07-20  9:49         ` Michael Clark
2018-07-19 15:56     ` Jeff Law
2018-07-19 16:12       ` Eric Gallager
2018-07-20 10:05       ` Martin Liška
2018-07-18 15:13 ` Boris Kolpackov
2018-07-18 16:56   ` Paul Koning
2018-07-18 17:29     ` Boris Kolpackov
2018-07-18 17:44       ` Paul Koning
2018-07-18 18:11         ` Matthias Klose
2018-07-20 11:04           ` Martin Liška
2018-07-19 14:47     ` Konovalov, Vadim
2018-07-23 14:21 ` Joseph Myers
2018-07-27 14:31 ` Michael Matz
2018-07-27 14:38   ` Michael Matz
2018-07-28  3:01     ` Matthias Klose
2018-07-27 14:54   ` Joseph Myers
2018-07-27 15:11     ` Michael Matz
2018-07-28  0:26       ` Paul Smith
2018-07-30 14:34         ` Joseph Myers
2018-07-28 12:11     ` Ramana Radhakrishnan
2018-07-28 17:23       ` David Malcolm
2018-07-30 14:51       ` Joseph Myers
2018-07-30 16:29         ` Andreas Schwab
2018-07-28  2:29 ` konsolebox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F0F29197-FEE7-49D7-B936-79878C441CD1@comcast.net \
    --to=paulkoning@comcast.net \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).