Xref: utzoo comp.lang.c:35708 comp.lang.fortran:4648 comp.unix.programmer:956 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!seismo!uunet!charyb!dan From: dan@kfw.COM (Dan Mick) Newsgroups: comp.lang.c,comp.lang.fortran,comp.unix.programmer Subject: Re: f2c table limit error Message-ID: <1991Feb1.195943.15456@kfw.COM> Date: 1 Feb 91 19:59:43 GMT References: <785@utrcu1.UUCP> <786@utrcu1.UUCP> Reply-To: dan@kfw.com (Dan Mick) Organization: KFW Corporation, Newbury Park, CA Lines: 40 In article <786@utrcu1.UUCP> emmerik@utrcu1.UUCP (Emmerik P.J.L. van) writes: >In article <785@utrcu1.UUCP>, emmerik@utrcu1.UUCP (Emmerik P.J.L. van) writes: >> >> Using f2c, i have the following problem: >> >> $ f2c tesfil.f >> testfil.f: >> testfil: >> Compile error line 13 of ../include/paramdefs.ii0: Too many names. >> Table limit now 401. >> Try recompiling using the -Nn802 option >> >> I am using f2c version 27 june 1990, created on an APOLLO using >> Domain/OS Version 10.1. >> >Most answers told me just to add a -Nn802 option to the command as >suggested in the message (-Nn802 being an undocumented f2c option). -Nn is right there in my manpage for f2c; if it's really not in yours, best get the latest version. >The reason this was not obvious to me (in fact i tryed it) is that i >used the f2c sources created on an Apollo system (the sources include a >YACC file) compiled an runned them on a VAX/VMS system. >Becouse VAX/VMS systems do not handle upper and lowercase characters the >way UNIX systems do, f2c did not get the message. >Fiddeling a bit the following worked: > f2c:==$f2c.exe > f2c "-Nn802" filename > > f2c -Nn802 filename >results in the message: > Error on line 0: Invalid flag '-nn802' ...which didn't immediately make you think "Why did it translate -Nn to -nn?"? Why not? Why, after seeing that, didn't you immediately think "Oh, this isn't an f2c problem at all?" Simple problem analysis saves a lot of net dollars, not to mention saving a lot of your time...