From: rixed@happyleptic.org
To: guile-user@gnu.org
Subject: Re: A bit further toward the flamewar
Date: Thu, 13 Oct 2011 20:54:24 +0200 [thread overview]
Message-ID: <20111013185424.GA17999@yeeloong.happyleptic.org> (raw)
In-Reply-To: <87r52hc6hu.fsf@gnu.org>
Your critique about C values that can be made invalid (through lack of
proper initialization or erroneous cast) are of course valid but sounds
quite rhetorical, since in practice, in my experience, this does not
cause many bugs (yet I'm sure you could site several examples of such
bugs). What's of more practical importance to me is that when you
change a data structure somewhere you can be confident that the compiler
will spot every other places where your changes require other changes.
You have not this safety with Scheme, and this is much more problematic
; again, in my experience. You have to run your code with all possible
inputs in order to make certain that you did not forget to propagate
your changes somewhere. This happened to me again two weeks ago when I
decided that my small guile-agentx library should use bytevectors
instead of strings to read/write from the socket. This small change had
many other small impacts but I was alone to find them, had to run the
code in many different situation to test many path before I gained
enough confidence that I didn't forgot some string operation somewhere
- yet this is a very small library!
Of course, I'm a beginner in Scheme so that might explain why my brain
lacks the necessary equipment to typecheck myself ; while my first
hello.c was written more than 20 years ago so maybe that's why I find C
quite safe in practice.
So, all in all, who knows? But I for sure would like to see type
annotations added in guile some day :-)
next prev parent reply other threads:[~2011-10-13 18:54 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
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 [this message]
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=20111013185424.GA17999@yeeloong.happyleptic.org \
--to=rixed@happyleptic.org \
--cc=guile-user@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).