home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.edu:1574 comp.lang.fortran:3473 comp.lang.misc:2970 comp.arch:9282 sci.math:11122
- Path: sparky!uunet!spool.mu.edu!agate!overload.lbl.gov!lll-winken!lll-crg.llnl.gov!blair
- From: blair@lll-crg.llnl.gov (Gary Blair)
- Newsgroups: comp.edu,comp.lang.fortran,comp.lang.misc,comp.arch,sci.math
- Subject: Re: Re: Scientists as Programmers (was Re: Small Language Wanted)
- Message-ID: <135691@lll-winken.LLNL.GOV>
- Date: 8 Sep 92 16:08:19 GMT
- References: <1992Sep3.112944.20996@dbsun.uucp> <Bu08uF.HBC@mentor.cc.purdue <KERS.92Sep4154056@cdollin.hpl.hp.com>
- Sender: usenet@lll-winken.LLNL.GOV
- Followup-To: comp.edu
- Distribution: na
- Organization: Lawrence Livermore National Laboratory
- Lines: 24
- Nntp-Posting-Host: lll-crg.llnl.gov
-
- In article <KERS.92Sep4154056@cdollin.hpl.hp.com> kers@hplb.hpl.hp.com (Chris Dollin) writes:
- >In article ... fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON) writes:
- >
- > C++ allows you to overload existing operators, although to make compiler
- > writer's jobs easier, it does not allow you to introduce new operators.
- >
- >Make that ``trivially easier''. So far as I am able to tell, the difficulty of
- >allowing the user to add new operator definitions is rather close to zero, so
- >long as this is taken into account *before* designing the language and
- >compiler. (C++ has the problem of trying to incorporate the lexical structure
- >of C.)
- >
-
-
- Wrong. If your compiler uses ANY kind of table-driven parsing scheme, it is
- next to impossible to allow programmer-defined operators. The parser must
- know what an operator looks like, and what precedence it has with respect
- to all other operators. This is usually predetermined, at
- compiler-generation time.
- --
- Gary J. Blair (510) 422-6675 blair@dancer.llnl.gov
- Lawrence Livermore National Laboratory
- P.O. Box 808, L-156
- Livermore, CA 94550
-