unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: rixed@happyleptic.org
To: guile-user@gnu.org
Subject: A bit further toward the flamewar
Date: Thu, 13 Oct 2011 13:27:09 +0200	[thread overview]
Message-ID: <20111013112709.GA28078@ccellier.rd.securactive.lan> (raw)
In-Reply-To: <8739exry15.fsf@pobox.com>

-[ Thu, Oct 13, 2011 at 12:22:46PM +0200, Andy Wingo ]----
> Much respect to the late Ritchie, but C is a dangerous language that has
> negative impacts on the real world.  We need to stop writing code that
> launches the missiles (or, more likely, installs malicious keylogging
> darknets) if your program has an out-of-bounds array write.  Guile helps
> people move from C to safe languages, at their own pace :)

Scheme is safer than C, because:

- It has garbage collection, which solves many trivial memory management bugs;
- A buggy program that performs an out-of-bound array access will crash
  at runtime, which is sometime better than to proceed.
- It's much more portable than C, so that porting a program from its
  developer machine to another one is very unlikely to introduce a
  bug.

C is safer than Scheme, because:

- It has no automatic memory management, which avoids a few tricky
  memory leaks;
- A buggy program that performs an out-of-bound array access may proceed
  with wrong data, which is sometime better than to crash at runtime;
- It has a type checker ; if not state of the art, it still stops you
  from using the wrong type in runtime most of the time.

I fail to see why Scheme is intrinsically safer than C, but as I just
learnt the death of Denis Ritchie it might be that I'm emotionally biased,
so to speak.




  reply	other threads:[~2011-10-13 11:27 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       ` rixed [this message]
2011-10-13 14:26         ` A bit further toward the flamewar 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
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=20111013112709.GA28078@ccellier.rd.securactive.lan \
    --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).