Path: utzoo!attcan!uunet!seismo!dimacs.rutgers.edu!mips!daver!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.std.c++ Subject: Re: overloading vs. virtual functions Message-ID: <27CC33DC.5222@tct.uucp> Date: 27 Feb 91 22:34:03 GMT References: <1991Feb19.051123.5198@gpu.utcs.utoronto.ca> <27C2D4B8.3AD3@tct.uucp> Organization: Teltronics/TCT, Sarasota, FL Lines: 18 According to dsouza@optima.cad.mcc.com (Desmond Dsouza): >In discussing programming language features, "orthogonal" has a more >specific meaning. Here is one (from M. Jazayeri, "Programming Language >Concepts", p.15) : > > The principle of 'orthogonality': language features can be > composed in a free and uniform manner with predictable effects > and without limitations. > >i.e. any meaningful composition of language constructs should be allowed. I cannot accept this definition. It is too broad for useful dialogue. Unless, of course, the statement ``No currently existing computer language is orthogonal'' is useful dialogue. :-) -- Chip Salzenberg at Teltronics/TCT , "It's not a security hole, it's a SECURITY ABYSS." -- Christoph Splittgerber (with reference to the upage bug in Interactive UNIX and Everex ESIX)