Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.unix.programmer,comp.lang.c Subject: Re: Odd compiler behaviour? Date: Sun, 06 Mar 2016 12:44:41 +0000 Lines: 13 Message-ID: <87k2lfvkqu.fsf@doppelsaurus.mobileactivedefense.com> References: <20160301061135.783@kylheku.com> <87h9gqb0lj.fsf@mantic.terraraq.uk> <878u22aua9.fsf@mantic.terraraq.uk> <87wpplaojy.fsf@mantic.terraraq.uk> <20160305152935.13fa72e4c5e160164248c79c@speakeasy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net 9C3ZEwyN8OWK9S5klA5AeARmp/PGy26PkM4Y8eMtYoRGgQYGM= Cancel-Lock: sha1:WjTnLAcC+FsdCt33P0o4ZbtI2fg= sha1:QFdKtRVp3ZUkyGQ0lRYQdCFruN8= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Xref: csiph.com comp.unix.programmer:8030 comp.lang.c:83294 "James K. Lowden" writes: [...] > C++ is sometimes criticized for overloaded operators, but IMO the > criticism should go the other way, because types exist to be operated > on. Any language that supports user-defined types but not user-defined > operators is missing an essential component. "Operators" are nothing but a weird, traditional (shorthand) infix notation for applying certain functions to certain arguments. The only thing they really have going for themselves is that - starting with elementary school - everybody is forced to learn them.