[Issue 52] ambiguous function pointer silently accepted

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=52





------- Comment #3 from wbaxter at gmail.com  2006-11-28 19:33 -------
(In reply to comment #2)
> Has there been any bug/enhancement filed on this that I can keep a watch on?

Sorry, obviously this is the bug (I just did a sloppy c&p from newsgroup
article digitalmars.com digitalmars.D:44742 ).

And if it's not clear what the problem is above, it's that the ''standard D
idiom'' to define property methods like:

    int value() { return m_value; }
    int value(int v) { return m_value=v; }

I use this in Luigi everywhere (http://www.dsource.org/projects/luigi).
I also use signals and slots in Luigi.  I've got a very handy automatic slot
wrapper mechanism that will let you connect any slot with a _compatible_
signature to a signal.  The slot doesn't have to have a void return type, for
example.  This is handy because it lets you connect the 'value' property above
directly to the signal (or at least apparently so from the users perspective).


--