Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Beta 18 Compilation Problem Under Nextstep 3.3

X-seq: zsh-workers 1115
From: joda@xxxxxxxxxx (Johan Danielsson)
To: Mark Borges <mdb@xxxxxxxxxxxx>
Subject: Re: Beta 18 Compilation Problem Under Nextstep 3.3
Date: 22 May 1996 02:45:46 +0200
Cc: zsh-workers@xxxxxxxxxxxxxxx
In-reply-to: Mark Borges's message of 21 May 1996 17:36:12 -0600
References: <Pine.NXT.3.93.960521144604.28147A-100000@racoon> <vkrasdwqdv.fsf@xxxxxxxxxxxx>

Mark Borges <mdb@xxxxxxxxxxxx> writes:

> Anyway, I backed out the change (why is it necessary to escape the
> `#else'?) and it worked fine.

Hmm, it was my patch for UNICOS, that somehow has a bug in awk.

$ uname -a
kallsup kallsup 9.0.2.0 roo.2 CRAY J90
$ echo | awk '{ print "#else" }'
bad switch yylook 79

Older awks printed a literal backslash when it wasn't followed by a
"legal" character, newer awks removes the backslash.

$ uname -a
SunOS sunsite.nada.kth.se 5.4 Generic_101945-32 sun4d sparc
$ echo | awk '{ print "\z" }' 
\z
$ echo | nawk '{ print "\z" }' 
z
$ echo | gawk '{ print "\z" }'
z

/Johan

References:
- Beta 18 Compilation Problem Under Nextstep 3.3
  - From: Irving Wolfe
- Re: Beta 18 Compilation Problem Under Nextstep 3.3
  - From: Mark Borges

Messages sorted by: Reverse Date, Date, Thread, Author