Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!gatech!udel!princeton!cs!samadams!tr
From: tr@samadams.princeton.edu (Tom Reingold)
Newsgroups: comp.lang.c
Subject: Re: hardcopy/productivity inverse correlation
Message-ID: <4768@rossignol.Princeton.EDU>
Date: 29 Nov 90 18:28:00 GMT
References: <46@resumix.UUCP> <5940050@hpcupt1.cup.hp.com> <28762@shamash.cdc.com> <6780@uceng.UC.EDU> <6785@uceng.UC.EDU>
Sender: news@cs.Princeton.EDU
Distribution: usa
Organization: Noo Joizy -- The Cultural Mecca
Lines: 20

dmocsny@minerva.che.uc.edu (Daniel Mocsny) writes:
$ No compiler should simultaneously permit (1) programs of more than
$ 20 lines and (2) undeclared variables.

In article <6785@uceng.UC.EDU> schriste@uceng.UC.EDU (Steven V.
Christensen) writes:

$ I understand (2), but why (1)? There is a lady with whom I work who
$ insists on breaking up even the simplest procedure into many sub-procs
$ (this is FORTRAN). In combination with ridiculously long proc and variable
$ names, it makes it even harder to debug...

I am pretty sure Dan meant logical "and".  (There goes someone else
claiming to know what Dan meant.) In other words, no compiler should
allow both of these things at the same time.
--
        Tom Reingold
        tr@samadams.princeton.edu  OR  ...!princeton!samadams!tr
        "Warning: Do not drive with Auto-Shade in place.  Remove
        from windshield before starting ignition."