Re: Is this good use of Properties?

I could declare it as static but only one instance of this class will ever
exists. Given that scenario, isn't that basically the same as declaring it
static?

What are some of your reasons for saying the VB compiler is brain dead? I'm
always interested in the detailed differences between C# and VB.NET and
where one is better than the other.

Thanks,
Brett

"Bob Powell [MVP]" <bob@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OEAGOtJVFHA.3636@xxxxxxxxxxxxxxxxxxxxxxx
> The C# compiler, unlike the brain-dead VB compiler, can figure out for
> itself that if a property only has a get accessor then it's probably a
> read-only property. It's one of my VB pet hates.
>
> Perhaps the type of property you mention would be better as a static
> property similar to Pi in the Math class or "Red" in the Color class.
>
> --
> Bob Powell [MVP]
> Visual C#, System.Drawing
>
> Find great Windows Forms articles in Windows Forms Tips and Tricks
> http://www.bobpowell.net/tipstricks.htm
>
> Answer those GDI+ questions with the GDI+ FAQ
> http://www.bobpowell.net/faqmain.htm
>
> All new articles provide code in C# and VB.NET.
> Subscribe to the RSS feeds provided and never miss a new article.
>
>
>
>
>
> "Brett" <no@xxxxxxxx> wrote in message
> news:%23Cry0lJVFHA.2172@xxxxxxxxxxxxxxxxxxxxxxx
>> If I do this without declaring a corresponding field, is it considered
>> bad design? What are the advantages or disadvantages to either method?
>> Notice there is not set.
>>
>> public string URL
>> {
>> get
>> {
>> return "www.somewhere.com/test.aspx";
>> }
>> }
>>
>> vs. a more common approach:
>>
>>
>> private readonly string _URL = "www.somewhere.com/test.aspx";
>>
>> public string URL
>> {
>> get
>> {
>> return _URL;
>> }
>> }
>>
>> Also, if I only have a get accessor, is it necessary to declare the field
>> as readonly?
>>
>> Thanks,
>> Brett
>>
>
>


.

Relevant Pages

  • Re: Is this good use of Properties?
    ... Overloads can also be inferred by the compiler ... Find great Windows Forms articles in Windows Forms Tips and Tricks ... >I could declare it as static but only one instance of this class will ever ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: advice on package design
    ... > for following scope. ... the compiler would have to do ... the extra verbiage required just to declare X. ... Unfortunately this is also untrue in Ada. ...
    (comp.lang.ada)
  • Re: Properties
    ... Is there any reason why this would not work and not simplify the ... Why should I have to declare any variable most of the time? ... The reason you explicitly declare fields used by a property is that the ... compiler needs to know what the code in the property does. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: use of erf intrinsic
    ... while it is also legal to declare a referenced function ... within the calling functionor even block, a la classic FORTRAN, ... The implementation (compiler) is required to check that references ... If you use K&R1 syntax, the compiler is not required to detect ...
    (comp.lang.fortran)
  • Re: Primitive curiosity...
    ... those types after the compiler has already used the information. ... "dispatch table" or something like that. ... contains the addresses of the primitive subprograms of the type. ... When you declare a type extension, ...
    (comp.lang.ada)
Loading