From: arnold@skeeve.com
To: 9fans@9fans.net
Subject: Re: [9fans] [GSOC 2013] Implement plan9 commands in Go, Goblin
Date: Mon, 29 Apr 2013 13:27:53 -0600 [thread overview]
Message-ID: <201304291927.r3TJRrDf006314@freefriends.org> (raw)
In-Reply-To: <CAEAzY3904Ea6hCRwXOC-KunxCp+HVyTqWVGN5+AVq5E4xHPp3A@mail.gmail.com>
Aram Hăvărneanu <aram.h@mgk.ro> wrote:
> Alternatively, one can implement rc(1) or awk(1) in Go, rather than
> implementing all the base tools.
Speaking from experience, there are a fair number of dark corners
to handle if you are going to implement awk. Contact me off list for
pointers to documentation and test suites.
Is there even a yacc equivalent from Go? That might be a reasonable
project - add Go support to Berkely Yacc, Plan 9 Yacc, or Bison. Or larger
in scale, to implement Yacc itself in Go.
Arnold
next prev parent reply other threads:[~2013-04-29 19:27 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 18:47 Alex-P. Natsios
2013-04-29 18:53 ` Alex-P. Natsios
2013-04-29 18:59 ` erik quanstrom
2013-04-29 19:11 ` Aram Hăvărneanu
2013-04-29 19:17 ` erik quanstrom
2013-04-29 19:27 ` arnold [this message]
2013-04-29 19:31 ` Aram Hăvărneanu
2013-04-29 19:33 ` Aram Hăvărneanu
2013-04-30 5:42 ` Jens Staal
2013-04-30 8:11 ` Bence Fábián
2013-04-30 9:00 ` Alex-P. Natsios
2013-04-30 15:26 ` Aram Hăvărneanu
2013-04-30 15:31 ` erik quanstrom
2013-04-30 15:41 ` Kurt H Maier
2013-04-30 15:44 ` Bence Fábián
2013-04-30 15:46 ` tlaronde
2013-04-30 18:18 ` Steve Simon
2013-04-30 21:03 ` Steve Simon
2013-04-30 22:23 ` suharik
2013-04-30 22:25 ` erik quanstrom
2013-04-30 22:50 ` suharik
2013-04-30 22:54 ` erik quanstrom
2013-04-30 23:44 ` suharik
2013-04-30 23:50 ` Brantley Coile
2013-05-01 0:56 ` erik quanstrom
2013-05-01 5:05 ` Matthew Veety
2013-05-03 13:31 ` Yaroslav
2013-04-30 21:03 ` Paul Patience
2013-05-01 6:49 ` tlaronde
2013-04-30 12:28 ` erik quanstrom
2013-04-29 19:00 ` Aram Hăvărneanu
2013-04-29 19:52 ` andrey mirtchovski
2013-04-29 19:58 ` erik quanstrom
2013-04-29 20:22 ` andrey mirtchovski
2013-04-29 20:00 ` Aram Hăvărneanu
2013-04-29 20:02 ` erik quanstrom
2013-04-29 22:45 ` Kurt H Maier
2013-04-29 21:59 ` andrey mirtchovski
2013-05-01 9:30 ` mortdeus
2013-05-01 10:58 ` mortdeus
2013-05-01 11:13 ` Alex-P. Natsios
2013-05-01 13:38 ` mortdeus
2013-05-02 0:02 ` erik quanstrom
2013-05-02 0:11 ` andrey mirtchovski
2013-05-02 1:01 ` Devon H. O'Dell
2013-05-02 1:06 ` erik quanstrom
2013-05-02 1:57 ` Lyndon Nerenberg
2013-05-02 3:34 ` Matthew Veety
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201304291927.r3TJRrDf006314@freefriends.org \
--to=arnold@skeeve.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).