Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!pacbell.com!att!cbnewsu!att!cbnews!lvc
From: lvc@cbnews.att.com (Lawrence V. Cipriani)
Newsgroups: comp.unix.shell
Subject: Re: awk to C (was awk)
Summary: limitations of awkcc
Keywords: (n)awk to C
Message-ID: <1990Oct5.121442.13720@cbnews.att.com>
Date: 5 Oct 90 12:14:42 GMT
References: <8678@mirsa.inria.fr> <3802@network.ucsd.edu> <92@dlss2.UUCP> <1990Oct4.131446.28302@cbnews.att.com>
Organization: Ideology Busters Inc.
Lines: 16

In article <1990Oct4.131446.28302@cbnews.att.com>, lvc@cbnews.att.com (Lawrence V. Cipriani) writes:
> Yes.  There is one in the AT&T Toolchest called awkcc.  See my previous
> post for Toolchest phone number and login.

I feel obliged to post this email I received regarding awkcc from someone
who knows much more about it than I.

>     Awkcc generally is very useful but there problems to be encountered,
>     e.g. memory not freed NOR reused for closed pipes streams.
>     Ended up switching back to C after a brief look inside awkcc;

The author of awkcc Chris Ramming left AT&T for academia; I have no idea
if anyone is actively maintaining awkcc.
-- 
Larry Cipriani, att!cbvox!lvc or lvc@cbvox.att.com
           "Save a logger, eat an owl"