jacob navia <jacob@[EMAIL PROTECTED]
> writes:
> Ben Bacarisse wrote:
>> Maybe I missed the do***ent you mean.
>>
> http://www.q-software-solutions.de/~jacob/
> There you will find a link to the specifications.
Ah, yes. That says a little more but not really enough. For example
I don't see anything about not allowing
T &operator=(T&, T&);
lcc-win32 seems to reject
T &operator=(T&, T*);
but that is not explained. Is that a problem with the compiler or the
specification?
How many times is operator= called in these cases:
T &operator=(T& x, int i) { ... }
T a1[5] = {1,2};
T a2 = {3};
(T[2]){1,2};
struct S { T t; };
S s1 = {1};
S s2 = {.x = 2};
S as[5] = {1,2};
Is the following permitted:
const T x = 42;
x = 43;
The compiler allows it but the specifications says nothing about it.
What is the meaning of a pointer argument? What does the remark
"References can be replaced by arrays of length 1." mean?
After reading the specification, I have more questions than when I
started.
> It would be very good for everybody if you would develop them
> with me.
We disagree to much. I've already said I think it is a mistake to
consider initialisation as the same as assignment, for example. I
think we just see thing far too differently.
--
Ben.
|
