[Issue 412] overloaded function resolution with null parameter

d-bugmail at puremagic.com d-bugmail at puremagic.com
Mon Oct 9 05:36:27 PDT 2006


------- Comment #2 from benoit at tionex.de  2006-10-09 07:36 -------
(In reply to comment #1)
> Normally we use:
> alias char[] string;
> Name "String" implies a class,
> and typedef gives error below.

This shouldn't be a example in good programming style. It should show a
compiler behaviour, that I think is a bug.
In this case I WANT a typedef to be able to have different function overloads
in both cases. That is "typedef" is for. That does not work with alias.
But now it doesn't work if the first parameter is null. I think the compiler
should be so smart, that he also can make the decision in this case.


More information about the Digitalmars-d-bugs mailing list