🚀 go-pugleaf

In article <9206280057.AA06346@poseur.JPL.NASA.GOV>,
earle@poseur.jpl.nasa.gov writes:
|>   I think that "yacc -d gram.y" will always create "gram.c" with these
|> un-ANSI
|>   "extern char *malloc(), *realloc();" declarations if the "yacc" used
|> is not
|>   ANSI-compatible.  I got around the problem by manually re-generating
|> both
|>   gram.c/gram.h with Sun's C 1.1 "ayacc"; it didn't create the offending
|> lines
|>   like plain "yacc" does:
|>   ...

I put the following hack into twm's Imakefile:

*** /tmp/RCSAa25489     Mon Jun 29 10:22:36 1992
--- Imakefile   Tue Jun 23 13:31:54 1992
***************
*** 32,41 ****
--- 32,53 ----
  ComplexProgramTarget(twm)
  InstallNonExecFile(system.twmrc,$(TWMDIR))
  
+ #if HasGcc2
+ 
  gram.h gram.c: gram.y
        yacc $(YFLAGS) gram.y
+       sed -e '/extern char \*malloc(), \*realloc();/d' y.tab.c >gram.c
+       $(RM) y.tab.c
+       $(MV) y.tab.h gram.h
+ 
+ #else
+ 
+ gram.h gram.c: gram.y
+       yacc $(YFLAGS) gram.y
        $(MV) y.tab.c gram.c
        $(MV) y.tab.h gram.h
+ 
+ #endif
  
  clean::
        $(RM) y.tab.h y.tab.c lex.yy.c gram.h gram.c lex.c deftwmrc.c 

-- 
  Dipl.-Inform. Rainer Klute      klute@irb.informatik.uni-dortmund.de
  Univ. Dortmund, IRB
  Postfach 500500         |)|/    Tel.: +49 231 755-4663
D-W4600 Dortmund 50       |\|\    Fax : +49 231 755-2386