From: Noah Lavine <noah.b.lavine@gmail.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Fix Ecmascript's tree-il compiling
Date: Mon, 30 Apr 2012 12:17:07 -0400 [thread overview]
Message-ID: <CA+U71=Oc2JPfXsz4u5BHd1x7_0Q9nBmEKanxojAbfL+06D4n=w@mail.gmail.com> (raw)
In-Reply-To: <CAPjoZock8HBbejZ=TB5iJkat8xDJ-P4cfM_R6_5mW4wnGK4npw@mail.gmail.com>
I checked that this is correct and committed it to stable-2.0.
You can make small bugfixes now, but if you want to make larger
contributions to Guile, you'll need to sign a copyright assignment
form. This is because in U.S. copyright law, the author of a
copyrighted work (like software) has the most ability to sue other
people to protect their copyright. The Free Software Foundation makes
sure it owns the copyright to all GNU software so that it will be able
to defend them in court. (See
http://www.gnu.org/licenses/why-assign.html for more information.) If
you want assign your copyright, please email assign@gnu.org.
Andy and Ludovic, I hope this is the right thing to do. If not, please
let me know.
Thanks,
Noah
On Sun, Apr 29, 2012 at 3:40 AM, Nala Ginrut <nalaginrut@gmail.com> wrote:
> Our inner Ecmascript(also named Javascript for a historical reason)
> has broken for a long time since tree-il has been updated.
> When I try to implement a small language with Guile, I found that
> current parse-tree-il doesn't need a list as its arg anymore.
> And I changed the same line in
> language/ecmascript/compile-tree-il.scm, then it works again!
> No matter how many people interested in the inner ecmascript there be,
> I like it and I wish it enhance more.
> Anyway, multi-language is an interesting feature for Guile.
>
> Here's the patch.
next prev parent reply other threads:[~2012-04-30 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 7:40 [PATCH] Fix Ecmascript's tree-il compiling Nala Ginrut
2012-04-30 16:17 ` Noah Lavine [this message]
2012-05-01 17:00 ` Nala Ginrut
2012-05-02 21:54 ` Ludovic Courtès
2012-05-04 9:15 ` Nala Ginrut
2012-05-17 2:23 ` Nala Ginrut
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='CA+U71=Oc2JPfXsz4u5BHd1x7_0Q9nBmEKanxojAbfL+06D4n=w@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=nalaginrut@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).