Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!uunet!microsoft!jimad From: jimad@microsoft.UUCP (Jim ADCOCK) Newsgroups: comp.lang.c++ Subject: Re: complex float z = 1.0i2.2; Message-ID: <70716@microsoft.UUCP> Date: 15 Feb 91 20:15:17 GMT References: <1991Feb13.233418.26399@intellistor.com> Reply-To: jimad@microsoft.UUCP (Jim ADCOCK) Distribution: comp Organization: Microsoft Corp., Redmond WA Lines: 18 In article <1991Feb13.233418.26399@intellistor.com> wicklund@intellistor.com (Tom Wicklund) writes: >C and C++ are good at letting me do anything the language can do. C++ >has different rules for built-in types than classes which can be >annoying (do I write using built-in types and lose features of classes >or do I encapsulate built-in types within a class and suffer poor >code generator quality. I claim that poor code generation has more to do with today's compilers than the C++ language. The issues of C++ quality code generation is quite a bit different that C quality code generation, and compiler vendors haven't figured that out yet. Where the C++ language does have problems in generating quality code is in the poor control over aliasing, due in turn to pointer definitions that pre-date optimizing compilers. If the capabilities of references were expanded somewhat, people could avoid using pointers in the more common situations, and compilers could generate better code.