unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier-CRDzTM1onBSWkKpYnGOUKg@public.gmane.org>
To: lightning-mXXj517/zsQ@public.gmane.org
Cc: guile-devel-mXXj517/zsQ@public.gmane.org
Subject: Re: The Free Semantics Foundation
Date: Thu, 04 Sep 2014 21:39:41 -0400	[thread overview]
Message-ID: <jwv7g1ivoie.fsf-monnier+gmane.lisp.guile.devel@gnu.org> (raw)
In-Reply-To: CAKFjmdxCaUJvBpXv4m4r8Z3tewJnKp1JZ8-OjbSfaBt3+OSGPg@mail.gmail.com

> I have written this as a sort of manifesto for a project. The idea is to
> develop software for automating programming. If we can automate the
> production of concrete implementations of communications protocols, device
> drivers, language interpreters, etc, then we can change and combine such
> implementations much more easily. We could also secure systems by design:
> if all the code on an exposed interface in a communications or an operating
> system is automatically generated, then we can ensure that buffer overruns
> etc can't happen.

People have been doing that for ages.  E.g. describe your protocol in
some language, then auto-generate an implementation from it.
The "some language" needs to be precise enough that an implementation
can be generated from it, so typically this language ends up looking
pretty much like a programming language.  Maybe specialized to the task
at hand (that's called a Domain Specific Language, and is routine in the
Lisp world) or with a slightly different feel (e.g. logic programming),
but in the end, because it needs to be precise enough, it ends up
constraining the "autogenerated implementation" rather tightly.

Coding in C or Scheme is "writing a spec", and passing it to GCC or
Guile is "automatic generation of an implementation".


        Stefan

  reply	other threads:[~2014-09-05  1:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04  1:57 The Free Semantics Foundation Ian Grant
2014-09-04  2:21 ` William ML Leslie
     [not found]   ` <CAHgd1hHsXaa83Ga7q6K9qOQ0pM_rYsfM--noMwegy9Lt=UJgBg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-04 23:59     ` Ian Grant
2014-09-05  1:39       ` Stefan Monnier [this message]
2014-09-04 13:34 ` Stefan Monnier

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=jwv7g1ivoie.fsf-monnier+gmane.lisp.guile.devel@gnu.org \
    --to=monnier-crdztm1onbswkkpyngoukg@public.gmane.org \
    --cc=guile-devel-mXXj517/zsQ@public.gmane.org \
    --cc=lightning-mXXj517/zsQ@public.gmane.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).