Xref: utzoo comp.std.c++:346 comp.lang.c++:9730
Path: utzoo!attcan!uunet!nih-csl!lhc!adm!cmcl2!phri!cooper!aardvark
From: aardvark@cooper.cooper.EDU (Rob Horn )
Newsgroups: comp.std.c++,comp.lang.c++
Subject: Re: operator. and ideas for extensions in general
Message-ID: <2964@cooper.cooper.EDU>
Date: 27 Sep 90 17:36:23 GMT
References: <11388@alice.UUCP>
Organization: The Cooper Union (NY, NY)
Lines: 24

in article <11388@alice.UUCP>, bs@alice.UUCP (Bjarne Stroustrup) says:
> 
> (5) What is the impact on the rest of the language?
> 	Language complexity? Consequential changes? Compiler complexity?
> 	Compile time overheads? Run time overheads? Easy to teach?
> 	Will it break any existing code? Will its implementation force
> 	recompilation of existing code?
> 	(For operator.() I'd rate such impact minimal).

What about the case where someone decides to:

	int operator.(int i, int j) {
		return i*j;
		}
			.
			.
			.

	cout << 12.34 << "\n";

Will the compiler see 12.34 as a floating point number, or
as (int) 12 . (int) 34 ?

Just a thought.