The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com (Aharon Robbins)
Subject: [TUHS] awkcc source code available
Date: Thu, 19 Jan 2012 22:34:20 +0200	[thread overview]
Message-ID: <201201192034.q0JKYKjJ003051@skeeve.com> (raw)

Hi. I announced this in comp.lang.awk in December and tried to BCC
the TUHS list but it didn't seem to happen.  Here's the announcement
I posted.

Arnold
-----------------------------------------------
From: arnold@skeeve.com (Aharon Robbins)
Newsgroups: comp.lang.awk
Subject: AWKCC source now available
Date: Fri, 16 Dec 2011 12:27:39 +0000 (UTC)
Message-ID: <jcfdfr$qt9$1 at dont-email.me>

[ BCC to TUHS list, Brian Kernighan & Chris Ramming ]

	awk 'BEGIN { print "Sherman, set the wayback machine for 1988" }'

Hello All.

This note is to announce that through the valiant efforts of Brian Kernighan,
Alcatel-Lucent has been persuaded to make the source for awkcc available.
It can be found at:

	https://open-innovation.alcatel-lucent.com/projects/awkcc

You have to register (no cost) before being able to download, but
it's easy.  The license terms are at the site.  It's a straightforward
"for personal use" kind of license.

For those who don't know, awkcc is an adaptation of Unix awk to translate
nawk programs into C.  It was originally implemented by Chris Ramming (then
at Bell Labs, although no longer) circa 1988, and the source dist includes
some doc that Chris wrote.

Given how fast machines are these days, this program is mostly of
historical interest.  But it's nice to have this bit of Unix / awk history
generally available.  And, if you really need to turn an awk program into
C, this may provide a starting point.

Enjoy!
-- 
Aharon (Arnold) Robbins 			arnold AT skeeve DOT com
P.O. Box 354		Home Phone: +972  8 979-0381
Nof Ayalon		Cell Phone: +972 50 729-7545
D.N. Shimshon 99785	ISRAEL



                 reply	other threads:[~2012-01-19 20:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201201192034.q0JKYKjJ003051@skeeve.com \
    --to=arnold@skeeve.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 NNTP newsgroup(s).