C# enum and weird The private field 'SI.BitTorrent.Peer.clientChokeStatus' is never used error

[SpookyET]

I got private ChokeStatus clientChokeStatus;.
In the constructor i got clientChokeStatus = ChokeStatus.Choked; and it is
also used in a few other methods, but it keeps bitching The private field
'SI.BitTorrent.Peer.clientChokeStatus' is never used.

[SpookyET]

It is used, is not it? But it throws that warning/error.

namespace Test
{

class Tester
{
public static void Main()
{
Foo f = new Foo(null, 5);
f.Foobish();
}
}

enum Foobar
{
Item1,
Item2
};

public class Foo
{
Foobar foobar;

public Foo(string foo, int bar)
{
foobar = Foobar.Item1;
}

public void Foobish()
{
foobar = Foobar.Item2;
}
}
}

[Daniel O'Connell [C# MVP]]

"SpookyET" <no****@hotmail.com> wrote in message
news:opr7hzt3bi1s9n15@saturn...

It is used, is not it? But it throws that warning/error.

namespace Test
{

class Tester
{
public static void Main()
{
Foo f = new Foo(null, 5);
f.Foobish();
}
}

enum Foobar
{
Item1,
Item2
};

public class Foo
{
Foobar foobar;

public Foo(string foo, int bar)
{
foobar = Foobar.Item1;
}

public void Foobish()
{
foobar = Foobar.Item2;
}
}
}

A field is only considered used when readable. In this case you are simply
assigning to it, which is as good as a noop if the field is never read
from(the value in it doesn't matter to control flow, its just memory sitting
somewhere). I would assume you would want to expose the ChokeStatus
externally, in which case you should expose a property, or you have a use
for it internally somewhere, in which case you should ignore it until you
get around to checking it. If you are just tracking it so you can use it for
whatever purposes later, you can safely ignore this warning as well.

[SpookyET]

God, what I was thinking? You are right, and I knew this. ~3000 lines of
code gets you tired, confused, and unable to see simple things. I got rid
of some stuff, and now it is under 2000 LOC. I have fixed it. I have
forgot to add those methods because events are raised when a message of
being choked or interested is received/sent.

public bool IsClientChoked() {}
public bool IsPeerChoked() {}
public bool IsClientInterested() {}
public bool IsPeerInterested() {}

On Wed, 5 May 2004 00:16:09 -0500, Daniel O'Connell [C# MVP]
<[e-mail]> wrote:

"SpookyET" <no****@hotmail.com> wrote in message
news:opr7hzt3bi1s9n15@saturn...

It is used, is not it? But it throws that warning/error.

namespace Test
{

class Tester
{
public static void Main()
{
Foo f = new Foo(null, 5);
f.Foobish();
}
}

enum Foobar
{
Item1,
Item2
};

public class Foo
{
Foobar foobar;

public Foo(string foo, int bar)
{
foobar = Foobar.Item1;
}

public void Foobish()
{
foobar = Foobar.Item2;
}
}
}

A field is only considered used when readable. In this case you are
simply
assigning to it, which is as good as a noop if the field is never read
from(the value in it doesn't matter to control flow, its just memory
sitting
somewhere). I would assume you would want to expose the ChokeStatus
externally, in which case you should expose a property, or you have a use
for it internally somewhere, in which case you should ignore it until you
get around to checking it. If you are just tracking it so you can use it
for
whatever purposes later, you can safely ignore this warning as well.

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/