unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-user@gnu.org
Subject: Re: request: libguile to wrap getsid(2)
Date: Mon, 28 Dec 2009 11:11:03 +0000	[thread overview]
Message-ID: <878wcnfj5k.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <877hs8xbwi.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Sun, 27 Dec 2009 23:58:05 +0100")

Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> As years go by, i have come to venerate old code per se less and
> less.  I think it would be cool to write tools to distill the
> essence of old code, recasting into new code.  That is what
> compilers do, after all...

If the new compiler/translator framework in Guile 1.9.x is capable of
handling ECMAScript and elisp, it should certainly (in principle) be
able to handle slightly different variants of Guile Scheme.  So that
might be a good way of handling any recasting at runtime.  I believe it
also supports writing out recast code - although perhaps at the cost of
losing some formatting and comments.

>  Dreaming, i'd like to see compilers
> that go beyond:
>
>             compilation
>   source ---------------------> "executable" representation
>
> to
>
>   grok-db -----+<-------+
>                v        |
>             compilation |
>   source ---------------+----> "executable" representation
>
> where grok-db contains the analysis results of (this and other)
> source, both present and past.

Can you give an example of what grok-db might say?

Also note that grok-db is in a sense already present, in the source code
of the compiler.

Regards,
      Neil




  parent reply	other threads:[~2009-12-28 11:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-26 18:50 request: libguile to wrap getsid(2) Thien-Thi Nguyen
2009-12-27 12:46 ` Neil Jerram
2009-12-27 18:21   ` Neil Jerram
2009-12-27 23:01     ` Thien-Thi Nguyen
2009-12-27 22:58   ` Thien-Thi Nguyen
2009-12-27 23:33     ` Linas Vepstas
2009-12-29  1:08       ` Jeff Wilkinson
2009-12-28  6:34     ` Ken Raeburn
2009-12-28 12:25       ` Thien-Thi Nguyen
2009-12-28 11:11     ` Neil Jerram [this message]
2009-12-28 12:18       ` Thien-Thi Nguyen

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=878wcnfj5k.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-user@gnu.org \
    --cc=ttn@gnuvola.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).