From: Jim Blandy <jimb@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: GDB and scripting languages - which
Date: Wed, 14 Feb 2007 05:57:00 -0000 [thread overview]
Message-ID: <m3zm7hanmw.fsf@codesourcery.com> (raw)
In-Reply-To: <ufy9b5d3l.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Feb 2007 22:34:54 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Jim Blandy <jimb@codesourcery.com>
>> Date: Mon, 12 Feb 2007 09:25:09 -0800
>>
>> There's a lot about Lua I like. However, it doesn't have exceptions.
>
> I think you are mistaken: Lua does have exceptions, it just calls them
> ``fallbacks''.
When I search the manual at http://www.lua.org/manual/5.1/, I don't
see any references to 'fallbacks'. The Lua HISTORY file mentions
them, but they seem to be an operator overloading mechanism, not an
exception-handling mechanism. Where can I find documentation on
these?
>> My personal three language essentials are:
>>
>> - type-safety (programs get errors, not segfaults)
>> - automatic storage management (I don't need to call 'free'), and
>> - exception handling (I don't need to check for an error return code
>> if my response will be to simply report it up to my caller)
>
> By type-safety, do you mean that variables can hold different types of
> objects, and programs that apply operators to operands of wrong types
> are treated gracefully, then I think Lua qualifies.
The second clause: "programs that apply operators to operands of wrong
types are treated gracefully". Lua does qualify as a type-safe
language, and it does provide automatic storage management. (All the
scripting languages I've seen do.)
> Anyway, two advantages of Lua are:
>
> . It was designed from ground up to be primarily an extension
> language, not a general-purpose language that just happens to have
> C bindings for its interpreter; therefore it is small and
> efficient (by a large factor compared to Tcl, for example).
>
> . It's typeless and generally lacks the clutter that more
> ``complete'' programming languages require: type declarations,
> memory allocations, initialization before use, etc.
I agree with both of these.
Even if the exception issue is worked out, though, I'm still concerned
that Lua doesn't have as much momentum as Python. Python's wealth of
other libraries available (gui; graphing; networking) brings a lot of
potential with it. And there are a lot of programmers out there who
could just start scripting GDB the day Python support is committed.
next prev parent reply other threads:[~2007-02-13 19:00 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 [this message]
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
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=m3zm7hanmw.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.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