unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [GSoC] Bourne-shell compiler front-end for Guile
Date: Tue, 22 Mar 2016 21:18:01 +0200	[thread overview]
Message-ID: <20160322211801.595f63e7@debian-netbook> (raw)
In-Reply-To: <87fuvj5uwi.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]

On Mon, 21 Mar 2016 23:27:25 +0100
ludo@gnu.org (Ludovic Courtès) wrote:

> Hi Efraim,
> 
> Thanks for your proposal!
> 
> This project can be pretty fun, I think, and quite rewarding if it
> indeed allows us to get rid of a bunch of bootstrap binaries.
> 
> As I see it, the project covers mostly two areas:
> 
>   1. Lexing & parsing.  This compiler front-end will need a real parser
>      for the Bourne shell syntax, notably semicolon-separated command
>      sequences, pipes, brace-delimited blocks, functions, variables, and
>      ‘test’ and ‘[’.
> 
>      The available tools could be SILex + (system base lalr) (the latter
>      is part of Guile, the former is maintained separately; a copy can
>      be found in Guile-RPC for instance.)
> 
>   2. Run-time support: redirections, pipes, background execution, C-c
>      (SIGINT) and C-z (SIGTSTP), globbing, and so on.
> 
>      Guile provides just the basic here, and a little more with (ice-9
>      popen).  Scsh and its Guile port(s) provide a lot of that, so it
>      might be a good idea to see what can be stolen from these.
> 
> It may be that some of your CS classes cover some of this ground (a
> fairly common programming project here at university is to implement a
> small shell precisely because it covers several areas.)
> 
> How does that sound?
> 
> Perhaps one way to get started would be by looking at the available
> tools for #1, and experimenting with hacks for #2, possibly borrowing
> code from Scsh.
> 
> Thoughts?

Sounds like lots of fun, I'm really looking forward to it. And it sounds like
I'll need to dive deeper into bash to see what I get to implement

> 
> Thanks,
> Ludo’.
> 
> PS: Would be nice to have a second mentor on this, either officially or
>     unofficially (if you don’t want to have a to be known to Google…).
>     Any takers?  :-)



-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-03-22 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 12:22 [GSoC] Bourne-shell compiler front-end for Guile Efraim Flashner
2016-03-21 22:27 ` Ludovic Courtès
2016-03-22 19:18   ` Efraim Flashner [this message]
2016-03-23 14:05     ` Ludovic Courtès
2016-03-23 20:33       ` Efraim Flashner
2016-03-24 13:26         ` Ludovic Courtès

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160322211801.595f63e7@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).