C#

Urs Enzler wrote:

But maybe the compiler is smart enough

devidutta Pradhan wrote:

Can anybody just guide me the difference
between these two declaration in c#

int a;
a=0;


and int a=0;

what is the diffrence is this anyproblem with performance issue??

devidutta Pradhan wrote:

classA a=new classA();
a=FunctionXXX();


classA a=FunctionXXX();

khalidelmeknesi wrote:

are you missing a using directive or an assembly reference?

szolDat wrote:

I need to make the other threads recognize and not read the element that is being updated.

public class StreamLocker
{
    private MemoryStream _stream;
    private bool _isLocked;

    public StreamLocker(MemoryStream stream)
    {
        _stream = stream;
        _isLocked = false;
    }

    public MemoryStream LockStream()
    {
        lock (_stream)
        {
            if (_isLocked)
                return null; //if it is locked than just return null
                             //the caller can than continue with another instance
            return _stream; //if the caller gets a result than nobody else is working on it
        }
    }

    public void UnlockStream()
    {
        lock (_stream)
        {
            _isLocked = false;
        }
    }
}

szolDat wrote:

What happens if a thread checks if a MemoryStream is available, sees that it is, and starts reading it, then the control is passed to the main thread. The main thread starts writing it, and if it gets to the point where the other thread is reading it, then that thread will return false data.

szolDat wrote:

If I lock on a private object and not the MemoryStream itself, then how can I make sure that no one is reading that object?