From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: A bit further toward the flamewar
Date: Thu, 13 Oct 2011 17:20:27 +0200 [thread overview]
Message-ID: <87r52grk90.fsf@pobox.com> (raw)
In-Reply-To: <87r52hc6hu.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 13 Oct 2011 16:26:37 +0200")
On Thu 13 Oct 2011 16:26, ludo@gnu.org (Ludovic Courtès) writes:
> Hello troll! ;-)
I think that's a bit harsh ;)
> Scheme is strongly, though dynamically typed. A string is a string, a
> number is a number, and they cannot change types anyhow.
As time goes on and I learn more things, I wonder how it is that "type"
has gotten so many conflations. This one certainly has value, but I
guess the CS world uses it in a different way, that types are theorems
about programs. A program that type-checks is has some corresponding
theorem that has a proof, and proving theorems about a program has value
in terms of reliability, &c. (It turns out that it doesn't matter much
which theorems are proven!)
Anyway this second, proof side of types, is the side that Scheme does
not have. C has a stronger story in that regard.
> And of course, this is not to mention the many other ways to shoot
> oneself in the foot–manual memory management being among the most
> prominent
This is what I meant when I said that C was dangerous. Programs in
Guile have meanings, even seemingly ill-formed programs like
((lambda () x))
Because what happens here? You get an exception. What happens in C if
you invoke puts without its argument? You might get a warning, but it
will compile, and at runtime /anything can happen/.
All programs of a sufficient size have bugs. The question is, what
happens when there is a bug? In Scheme, the answer isn't usually "the
Chinese/American/German government gets to read your email". With C it
is. That is why programming in C is dangerous.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-10-13 15:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 14:54 Why is guile still so slow? John Lewis
2011-10-12 15:39 ` rixed
2011-10-12 18:56 ` Jose A. Ortega Ruiz
2011-10-12 22:40 ` rixed
2011-10-12 23:56 ` Jose A. Ortega Ruiz
2011-10-13 6:23 ` rixed
2011-10-13 10:22 ` Andy Wingo
2011-10-13 11:27 ` A bit further toward the flamewar rixed
2011-10-13 14:26 ` Ludovic Courtès
2011-10-13 15:20 ` Andy Wingo [this message]
2011-10-13 16:30 ` Linas Vepstas
2011-10-13 18:37 ` Mike Gran
2011-10-13 21:42 ` Linas Vepstas
2011-10-13 22:08 ` dskr
2011-10-14 1:07 ` Ian Price
2011-10-14 8:40 ` Andy Wingo
2011-10-14 16:23 ` Linas Vepstas
2011-10-15 8:44 ` Andy Wingo
2011-10-14 8:28 ` Andy Wingo
2011-10-14 16:30 ` Linas Vepstas
2011-10-14 17:26 ` Andy Wingo
2011-10-13 19:16 ` Hans Aberg
2011-10-14 9:57 ` Panicz Maciej Godek
2011-10-13 17:43 ` Ludovic Courtès
2011-10-13 18:54 ` rixed
2011-10-13 21:14 ` Ludovic Courtès
2011-10-13 21:58 ` Hans Aberg
2011-10-14 9:28 ` Ludovic Courtès
2011-10-14 10:53 ` Hans Aberg
2011-10-14 9:37 ` rixed
2011-10-14 20:05 ` Ludovic Courtès
2011-10-12 15:52 ` Why is guile still so slow? Andy Wingo
2011-10-12 16:19 ` John Lewis
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r52grk90.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).