Click here to Skip to main content
Sign Up to vote bad
good
See more: C#4.0
I'm fond of the new .NET 4.0 optional parameters feature, but I've recently came across a limitation I do not understand.
 
Consider the following simple attribute:
class SomeAttribute : Attribute
{
	public SomeAttribute(string someString = null)
	{
	}
}
 
When I try to use the attribute in the statement [SomeAttribute()], the following error is generated on compiling:
 
"An attribute argument must be a constant expression, typeof expression or array creation expression of an attribute parameter type."
 
This strikes me as odd, since the default argument IS a constant expression.... And even stranger is the following:
The code can compile when I change null to "", or when I remove the part : Attribute, and call for instance new SomeAttribute(). I'm clueless....
 
Can someone explain me why this error is generated and not in the other case?
And are there any workarounds, besides creating all sorts of constructor overload(like in .NET versions before 4.0)?
Posted 12 Jul '10 - 7:21
Edited 12 Jul '10 - 7:43


1 solution

Looks like a compiler bug to me, and worth reporting on Connect. Meanwhile, here's a workaround:
 
class SomeAttribute : Attribute
{
    public const string pnull = null;
 
    public SomeAttribute(string someString = pnull)
    {
    }
}
 
[SomeAttribute()]
class App
{
    static void Main()
    {
    }
}
  Permalink  

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Your Filters
Interested
Ignored
     
0 Sergey Alexandrovich Kryukov 415
1 OriginalGriff 315
2 Slacker007 240
3 Maciej Los 240
4 Aarti Meswania 210
0 Sergey Alexandrovich Kryukov 8,953
1 OriginalGriff 7,134
2 CPallini 3,758
3 Rohan Leuva 3,066
4 Maciej Los 2,528


Advertise | Privacy | Mobile
Web02 | 2.6.130516.1 | Last Updated 12 Jul 2010
Copyright © CodeProject, 1999-2013
All Rights Reserved. Terms of Use
Layout: fixed | fluid