Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.14 $; site uiucdcs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!ihnp4!inuxc!pur-ee!uiucdcs!liberte
From: liberte@uiucdcs.UUCP
Newsgroups: net.unix
Subject: Re: Neophyte awk question(s)
Message-ID: <39300016@uiucdcs.UUCP>
Date: Tue, 25-Sep-84 02:32:00 EDT
Article-I.D.: uiucdcs.39300016
Posted: Tue Sep 25 02:32:00 1984
Date-Received: Wed, 26-Sep-84 19:42:29 EDT
References: <487@loral.UUCP>
Lines: 15
Nf-ID: #R:loral:-48700:uiucdcs:39300016:000:672
Nf-From: uiucdcs!liberte    Sep 25 01:32:00 1984

I discovered this awk-wardness a while ago and reported a bug fix
in net.bugs.4bsd to allow awk programs to use \nnn as well as
\f \b \r \n and \\ in all strings or character literals.  The problem
isnt in printf as it would seem since translation to the corresponding
ascii code is done during compilation of the strings, not during output.
I will resend my fix to whoever is interested.

One way to get around the problem without modifying `awk` is to
use something like:  printf "%c", 1.  However, this is often awkward.


Daniel LaLiberte          (ihnp4!uiucdcs!liberte)
U of Illinois, Urbana-Champaign, Computer Science
{limit your limits;  extend your extensions?}