Welcome to the Lounge

LOOP
    statements        // Can be empty

EXITIF condition      // You can have any number of EXITIF statements

    statements        // Can be empty

// Repeat as many EXITIF clauses as you want
EXITIF condition

    statements        // Can be empty
ENDLOOP

LOOP
EXITIF NOT condition
      statements
ENDLOOP

LOOP
      statements
EXITIF condition
ENDLOOP

cv = initialvalue
LOOP
EXITIF cv > endvalue
      statements
      cv = cv + increment
ENDLOOP

found = noofitemsinarray   // Assume elements are 0..(noofitemsinarray-1)
LOOP
      found = found - 1
EXITIF found < 0
EXITIF array(found) = itemtofind
ENDLOOP
// found = -1 if not in array, or >= 0 for found location

if (mylist.Contains(refKey)
{
  refKey.refcount++; 
}
else
{
  mylist.Insert(refKey);
  refKey.refcount++;
}

Member 7989122 wrote:

OK, my point was not to illustrate how to insert an element into a list, but to illustrate a mechanism.

public class ElementReferenceCounter
{
    private readonly Dictionary<string, ListElt> elements;
    
    public Elements()
    {
        elements = new Dictionary<string, ListElt>();              
    }

    public void AddOrIncrementRefCount(string refKey)
    {
        if (elements.ContainsKey(refKey))
        {
            elements[refKey].RefCount++;
        }
        else
        {
            elements[refKey] = new ListElt(refKey, 0);
        }
    }

    public void DecrementRefCount(string refKey)
    {
        // you'd probably want to throw an exception here in real code
        if (!elements.ContainsKey(refKey)) return;

        // you might want to keep elements with 0 ref count, depending on 
        // your application's needs
        if(elements[refKey].RefCount == 1)
        {
            elements.Remove(refKey);
        }
        else
        {
            elements[refKey].RefCount--;
        }
    }  
}

myList.AddOrIncrementRefCount(refkey)

while ( true ) if ( ( ch = sr.Read() ) != -1 )
{
  System.Console.WriteLine ( "{0} {1} {2}" , i , ch , (char) ch ) ;

  if ( ch == 26 )
  {
    System.Console.WriteLine ( "Found a char 26 at offset {0}" , i ) ;

    break ;
  }

  i++ ;
}
else
{
  System.Console.WriteLine ( "Reached the EOF" ) ;

  break ;
}

# define whilst(x,y) while ( x ) if ( y )

...

int ch ;
int i = 0 ;

whilst ( sr.BaseStream.CanRead , ( ch = sr.Read() ) != -1 )
{
  System.Console.WriteLine ( "{0} {1} {2}" , i , ch , (char) ch ) ;

  if ( ch == 26 )
  {
    System.Console.WriteLine ( "Found a char 26 at offset {0}" , i ) ;

    sr.BaseStream.Close() ;
  }

  i++ ;
}
else
{
  System.Console.WriteLine ( "Reached the EOF" ) ;

  sr.BaseStream.Close() ;
}

glennPattonInThePUB wrote:

I must say a couple of places I interviewed at did have a print out of my CP article...

Quote:

There is a fundamental mismatch between a large companies' actual requirements and those that the recruiters apply, which leads to much frustration on both sides. Sigh |

1. We have to do work X now. Can this person do it with standards that we follow or like to achieve?
2. Once X is over, we need to work on Y and might also get Z to do. Will this person be useful then?
3. Does this person look like he can adapt to our work culture?
4. Is it probable that this person will be around as long as we would want him to be?
5. Does this person look like he is willing to learn new things or rather open to change and criticism?
6. He claims to be having X years of experience. Do we see expected maturity levels at this experience?*

1. Incompetent
2. Rigid in the way he works
3. Madly in love with technology he has worked with, hence not open for newer things.

Quote:

Does this person look like he can adapt to our work culture?