From: Robert Dewar <dewar@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jimb@codesourcery.com, gdb@sourceware.org
Subject: Re: GDB and scripting languages - which
Date: Wed, 14 Feb 2007 18:29:00 -0000 [thread overview]
Message-ID: <45D34E2E.7070701@adacore.com> (raw)
In-Reply-To: <utzxo4ok0.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Wed, 14 Feb 2007 11:01:39 -0500
>> From: Robert Dewar <dewar@adacore.com>
>> CC: Jim Blandy <jimb@codesourcery.com>, gdb@sourceware.org
>>
>> that's really pure FUD
>
> Thanks, this kind of attitude really helps to facilitate free
> expression of opinions on this list.
Well my use of the term FUD here was
considered. You were arguing that Python would
introduce excessive overhead, but with absolutely
no supporting data, or detailed argument. To me
a claim like that is definitely in the general
fear-uncertainty-doubt category, and is not
very helpful ... simple opinions are not very
useful unless they are grounded in some clear
facts.
My experience with Python (mostly in the context
of its use as a scripting language for GPS), is
that it is powerful, easy to use, and does not
introduce excessive overhead. The organization
of Python is modalar, lots of the capability is
in libraries which you only get if you access,
and having a python interpretor installed seems
like a more and more reasonable thing, given
the increasing popularity of this language for
many things.
next prev parent reply other threads:[~2007-02-14 18:01 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 22:20 Daniel Jacobowitz
2007-01-08 22:39 ` Kip Macy
2007-01-08 22:42 ` Daniel Jacobowitz
2007-01-08 23:03 ` Kip Macy
2007-01-08 22:40 ` Bob Rossi
2007-01-09 20:11 ` Jim Blandy
2007-01-09 20:23 ` Bob Rossi
2007-01-09 21:37 ` Paul Koning
2007-01-09 21:42 ` Daniel Jacobowitz
2007-01-09 21:48 ` Nick Roberts
2007-01-09 21:53 ` Daniel Jacobowitz
2007-01-11 4:31 ` Nick Roberts
2007-01-11 5:06 ` Daniel Jacobowitz
2007-01-13 8:30 ` Eli Zaretskii
2007-01-09 21:55 ` Kip Macy
2007-01-11 14:56 ` Robert Dewar
2007-01-11 15:07 ` Robert Dewar
2007-01-09 20:30 ` Mark Kettenis
2007-01-13 8:32 ` Eli Zaretskii
2007-02-10 12:28 ` Eli Zaretskii
2007-02-10 18:10 ` Pedro Alves
2007-02-10 20:33 ` Daniel Jacobowitz
2007-02-12 17:47 ` Jim Blandy
2007-02-12 21:36 ` Eli Zaretskii
2007-02-12 21:59 ` Robert Dewar
2007-02-12 22:07 ` Daniel Jacobowitz
2007-02-12 22:07 ` Robert Dewar
2007-02-14 5:57 ` Jim Blandy
2007-02-14 15:42 ` Eli Zaretskii
2007-02-14 16:01 ` Paul Koning
2007-02-14 17:50 ` Eli Zaretskii
2007-02-14 16:06 ` Daniel Jacobowitz
2007-02-14 18:01 ` Eli Zaretskii
2007-02-14 18:45 ` Daniel Jacobowitz
2007-02-14 17:37 ` Robert Dewar
2007-02-14 18:24 ` Eli Zaretskii
2007-02-14 18:29 ` Robert Dewar [this message]
2007-02-14 18:33 ` Eli Zaretskii
2007-02-14 18:34 ` Robert Dewar
2007-02-14 20:14 ` Jim Blandy
2007-02-14 20:56 ` Robert Dewar
2007-02-14 21:47 ` Jim Blandy
2007-02-14 21:23 ` Jim Blandy
2007-02-14 21:46 ` Robert Dewar
2007-02-14 20:10 ` Jim Blandy
2007-02-15 1:03 ` Gaius Mulley
2007-02-17 13:53 ` Eli Zaretskii
2007-02-17 14:07 ` Daniel Jacobowitz
2007-02-18 4:11 ` Robert Dewar
2007-02-19 22:17 ` Jim Blandy
2007-01-15 18:29 Kaz Kylheku
2007-01-15 21:20 ` Eli Zaretskii
2007-01-16 0:17 ` Kip Macy
2007-01-17 19:09 ` Jim Blandy
2007-01-16 0:38 Kaz Kylheku
2007-01-17 19:24 ` Jim Blandy
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=45D34E2E.7070701@adacore.com \
--to=dewar@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
/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