unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Ian Grant <ian.a.n.grant@googlemail.com>
To: guile-devel <guile-devel@gnu.org>,
	"Taylan Bayırlı" <taylanbayirli@gmail.com>,
	"William Leslie" <william.leslie.ttg@gmail.com>,
	"Richard Stallman" <rms@gnu.org>,
	"Mark H Weaver" <mhw@netris.org>
Subject: Re: Verifying Toolchain Semantics
Date: Sun, 5 Oct 2014 14:19:42 -0400	[thread overview]
Message-ID: <CAKFjmdyGF86af8jqn2WOeTA3-Oj5M=AOisAhgZgkMeQV6Sm0Lg@mail.gmail.com> (raw)
In-Reply-To: <CAKFjmdycYTv==RzErMAOYfS2PpCfX8PWrt23YtB2KykSYKU+gQ@mail.gmail.com>

On Sun, Oct 5, 2014 at 1:42 PM, Ian Grant <ian.a.n.grant@googlemail.com> wrote:
> [we] will be able to implement a C compiler in Microsoft Word BASIC, or in
> COBOL, and that will be capable of compiling GCC, if we had a year or
> so to wait while it does it ...

This is not true. Word BASIC or COBOL could easily write out an
executable binary defined by an abstract formal description in a text
file. It would take a while, but the binary would be able to compile
GCC pretty quickly.



  reply	other threads:[~2014-10-05 18:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-05 17:42 Verifying Toolchain Semantics Ian Grant
2014-10-05 18:19 ` Ian Grant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-06  0:30 Ian Grant
     [not found] ` <CAKFjmdzxAMvcry8N6B_atM_8vGyzA1Dfz9ygWxSgh3fD7EUAuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-06  8:51   ` William ML Leslie
2014-10-02 14:54 Ian Grant
2014-10-03  6:23 ` Mark H Weaver
2014-10-03  7:15   ` William ML Leslie
2014-10-03 12:56     ` Taylan Ulrich Bayirli/Kammer
2014-10-03 17:13       ` Mark H Weaver
2014-10-05 13:57       ` William ML Leslie
2014-10-03  8:45   ` Nala Ginrut
2014-10-05  1:35   ` Ian Grant
2014-10-05  5:39     ` Nala Ginrut
2014-10-05 14:14       ` Ian Grant
2014-10-05 15:15         ` Nala Ginrut
2014-10-05 16:24           ` Ian Grant
2014-10-06  8:25             ` Nala Ginrut
2014-10-05  6:58     ` Mike Gerwitz
2014-10-05 16:11       ` Ian Grant
2014-10-06  4:23         ` Mike Gerwitz
     [not found]           ` <20141006042323.GA31390-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-10-07 17:18             ` Ian Grant
     [not found]               ` <CAKFjmdx+jzfapvrq6EEO8Skx2L2UZwi-DZ22xiq9t1438E7kOw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-07 17:28                 ` Mark H Weaver
2014-10-07 17:56                   ` Ian Grant
     [not found]                     ` <CAKFjmdwNTjJ7nU-rKEWkA+5whsfyrpqJ6RkhU+VRbUW6rqT03A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-07 19:24                       ` Philip Herron
     [not found]                         ` <CAEvRbeoEJPTtoDu0nDudJyfBoaT1vpuvHzL=t+TkJr_ZGkzYEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-07 19:47                           ` Ian Grant
2014-10-08 18:26                       ` Mark H Weaver
2014-10-08  3:55               ` Mike Gerwitz

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='CAKFjmdyGF86af8jqn2WOeTA3-Oj5M=AOisAhgZgkMeQV6Sm0Lg@mail.gmail.com' \
    --to=ian.a.n.grant@googlemail.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.org \
    --cc=rms@gnu.org \
    --cc=taylanbayirli@gmail.com \
    --cc=william.leslie.ttg@gmail.com \
    /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).