home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!uicvm.uic.edu!u35395
- Organization: University of Illinois at Chicago
- Date: Fri, 22 Jan 1993 18:48:13 CST
- From: C. M. Sperberg-McQueen <U35395@uicvm.uic.edu>
- Message-ID: <93022.184813U35395@uicvm.uic.edu>
- Newsgroups: comp.lang.prolog
- Subject: Efficiency and 'good' Prolog (was: Help !!)
- References: <lenn.726916615@du9ds4>
- <j_hamer-210193105028@john-ha.cs.aukuni.ac.nz>
- <93021.154835U35395@uicvm.uic.edu> <1993Jan21.223806.19004@colorado.edu>
- Lines: 24
-
- > Because some of us do write large Prolog programs that depend on efficiency,
- > and it's better to instill good programming habits from the beginning than to
- > overcome bad programming practice later on.
-
- Proof, I guess, that using a logic programming language does not make us
- logical. If I were willing to accept your equation of 'good programming
- habits' with fast code, I wouldn't have posted my note about writing
- Prolog as though it were Pascal with commas. If you want to make anyone
- believe it, you should provide an argument or two in favor of it, not
- just say it again.
-
- The real problem for me in your note, however, is your assertion that
- relying on Prolog's declarative semantics is 'bad programming practice'.
- The relative clarity of its declarative interpretation is one of the
- most appealing things about Prolog -- God forbid we should begin to
- think of it as a 'bad habit' if we take advantage of one of the best
- features of the language!
-
- If you write big systems that have to be optimized to be fast, you have
- a right to worry about writing fast code. You do not have the right to
- spread the pernicious falsehood that speed is the only criterion of good
- code.
-
- -C. M. Sperberg-McQueen
-