opStarAssign?

[Leonard Dahlmann]

Janice Caron Wrote:

> On 11/22/07, Gregor Richards <Richards at codu.org> wrote:
> > Janice Caron wrote:
> > > but for some reason
> > > "opStar" would not be high on my list of choices.
> >
> > Because the names for operator overloads should be based on what
> > operator they're overloading, not the syntax for it.
> >
> > e.g. it's opMul, not opStar. opDiv, not opSlash.
> 
> Yeah. Um. I was employing irony.
> 
> Anyway, I'd hope Walter is considering changing the name, given the
> unanimous support here for doing that. The other part of my question
> though, was, is opWhateverAssign() on the cards any time soon. Any
> sign of an overload for *p = ?

What about *p *=, *p /=, *p ~=, ...?
Wouldn't these need overloads, too?