1: Write me a function that receives three integer inputs for the lengths of the sides of a triangle and returns one of four values to determine the triangle type (1=scalene, 2=isosceles, 3=equilateral, 4=error). Generate test cases for the function assuming another developer coded the function
Answer:
int GetCubicType(int Height, int Width, int Length)
{
if (Height < 0 || Width < 0 || Length < 0)
return 4;
else
{
if ((Height == Width) && (Height == Length))
return 3;
else
if ((Height == Width) || (Width == Length) || (Length == Width))
return 2;
else
return 1;
}
}
2: Implement a circular queue of integers of user-specified size using a simple array. Provide routines to initialize(), enqueue() and dequeue() the queue. Make it thread safe.
Answer:
using System;
using System.Threading;
namespace Test
{
/// <summary>
/// Summary description for CircularQueue
/// </summary>
public class CircularQueue
{
private int head;
private int tail;
private int[] queue;
private int length;
static Object QueueLock = new Object(); // will be used to make the Queue thread safe
/// <summary>
/// Queue constructor
/// </summary>
/// <param name="Length"> Queue needed Length</param>
public CircularQueue(int Length)
{
Initialize(Length);
}
/// <summary>
/// Empty Constructor for our test Cases
/// </summary>
public CircularQueue()
{
}
/// <summary>
/// Initializes the Queue to a specific given length
/// </summary>
/// <param name="Length"> The ne</param>
private void Initialize(int Length)
{
head = tail = -1;
this.length = Length;
queue = new int[Length];
}
/// <summary>
/// Adds a new int element to the end of the Queue
/// </summary>
/// <param name="value"> The integer vvalue of the element to be queued</param>
/// <returns>The index of the queued element or -1 on failure</returns>
public int Enqueue(int value)
{
lock (QueueLock)
{
if ((head == 0 && tail == length - 1) || (tail + 1 == head))
{
return -1; // Queue is full
}
else
{
if (tail == length - 1)
tail = 0;
else
tail++;
queue[tail] = value;
if (head == -1)
head = 0;
return tail;
}
}
}
/// <summary>
/// Gets the first element's value in the queue and removes it
/// </summary>
/// <returns> The element's value or -1 if the queue is empty</returns>
public int Dequeue()
{
lock (QueueLock)
{
int value;
if (head == -1)
{
value = -1;
}
else
{
value = queue[head];
queue[head] = 0;
if (head == tail)
head = tail = -1;
else
if (head == length - 1)
head = 0;
else
head++;
}
return value;
}
}
/// <summary>
/// Gets a formatted string of the queue elements
/// </summary>
/// <returns>Queue elements</returns>
public string ViewQueueElements()
{
lock (QueueLock)
{
int i;
string result = " Queue Emelemnts: ";
if (head == -1)
{
result = " No Elements Found !";
}
else
{
if (tail < head)
{
//for(i = head; i <= size - 1; i++)
for (i = 0; i <= length - 1; i++)
result += queue[i] + " ";
}
else
//for(i = head; i <= tail; i++)
for (i = 0; i <= tail; i++)
result += queue[i] + " ";
}
return result + "\n";
}
}
/// <summary>
/// For Console Application Test
/// </summary>
public void StartConsoleTest()
{
Initialize(3);
Enqueue(1);
Console.WriteLine();
Console.Write(ViewQueueElements());
Enqueue(2);
Console.WriteLine();
Console.Write(ViewQueueElements());
Enqueue(3);
Console.WriteLine();
Console.Write(ViewQueueElements());
Dequeue();
Console.WriteLine();
Console.Write(ViewQueueElements());
Dequeue();
Console.WriteLine();
Console.Write(ViewQueueElements());
Dequeue();
Console.WriteLine();
Console.Write(ViewQueueElements());
Console.WriteLine();
}
}
class Program
{
static void Main(string[] args)
{
CircularQueue circularQueue = new CircularQueue();
Thread[] threads = new Thread[1]; // you can use any number of threads
for (int i = 0; i < threads.Length; i++)
{
threads[i] = new Thread(new ThreadStart(circularQueue.StartConsoleTest));
}
for (int i = 0; i < threads.Length; i++)
{
threads[i].Start();
}
Console.WriteLine();
Console.Write(" Press any key to continue...");
Console.WriteLine();
Console.ReadLine();
}
}
}3: Memory model and generations
Offer a brief description (no more than 5-10 sentences) on the .NET memory model; identify it’s major features; identify generations and how they relate to the memory model and finally, what implications the memory model has for interoperability with legacy systems and code.
Memory model: It’s the abstraction that makes the reality of today’s exotic hardware comprehensible to software developers.
The reality of hardware is that CPUs are renaming registers, performing speculative and out-of-order execution, and fixing up the world during retirement. Memory state is cached at various levels in the systems.
The .NET memory model (on the .NET Framework) guaranteed that for certain types (most notably primitive integers and references) operations were guaranteed to be atomic.
Major Features:
|
4: Destructors
Define destructors, where and why they should be used and what implications they have in relation to finalizers.
Destructors are parameterless class methods (ex: ~ClassName() {}) that work on dumping and releasing the unmanaged resources used by the objects initiated from these classes, A class can have only one destructor and a class destructor can’t be called but it is invoked automatically.
Actually, we use destructors to do extra work on releasing unmanaged resources such as files and network connections; All the other managed resources are released automatically by the .Net Framework CLR using the finilizers that must be invoked in the destructors after we release the unmanaged resources.
|
5: Exceptions
What is an exception, what is the general pattern for using exceptions and why are they superior to return values?
Exception is a runtime error.
We use the try catch finally statements for exceptions handling, when an exception is thrown, The CLR returns an objects of Exception Type Class such InvalidOperationException for dividing by zero operations.
Every exception object returned has common properties to help us to identify and handle it such as the “Message” property that contains the runtime error message and the “StackTrace” that contains the full path of processing error to refer to the command that caused it.
|
6: Private Constructors
Can you have a private constructor? If so what would it be used for?
Yes, I used private constructors to control the objects initiation to apply the creational design patterns such as the factory pattern with a GetObject() method as the only public method to initiate objects in addition to singletons and other creational patterns.
|
7: C#
Difference between Copy and Clone
What is the difference between a copy and a clone in C#? Where does the ICloneable interface come in and what are the issues with it?
Copy: is used to copy the object’s complete structure as well as data.
Clone: is used to copy the object’s structure of a data only.
ICloneable can be found in the “System” namespace.
The problem with ICloneable is that it does not provide enough information. There is no way to know whether a Clone of an object will be a deep or shallow copy of the original, etc; In addition there is no Generic Types support as there is no “ICloneable<T>”.
|
8: Thread Safety
What is the difference between the ‘lock’ keyword and a monitor class? Write a class that demonstrates their use to protect access to a variable.
Lock is a simplified version of the monitor. Actually behind the scenes is doing the same thing.
This is an example developed for the last question of the MT Prospect Screen.doc
public class CircularQueue
{
private int head;
private int tail;
private int[] queue;
private int length;
static Object QueueLock = new Object(); // will be used to make the Queue thread safe
/// <summary>
/// Queue constructor
/// </summary>
/// <param name="Length"> Queue needed Length</param>
public CircularQueue(int Length)
{
Initialize(Length);
}
/// <summary>
/// Empty Constructor for our test Cases
/// </summary>
public CircularQueue()
{
}
/// <summary>
/// Initializes the Queue to a specific given length
/// </summary>
/// <param name="Length"> The ne</param>
private void Initialize(int Length)
{
head = tail = -1;
this.length = Length;
queue = new int[Length];
}
/// <summary>
/// Adds a new int element to the end of the Queue
/// </summary>
/// <param name="value"> The integer vvalue of the element to be queued</param>
/// <returns>The index of the queued element or -1 on failure</returns>
public int Enqueue(int value)
{
lock (QueueLock)
{
if ((head == 0 && tail == length - 1) || (tail + 1 == head))
{
return -1; // Queue is full
}
else
{
if (tail == length - 1)
tail = 0;
else
tail++;
queue[tail] = value;
if (head == -1)
head = 0;
return tail;
}
}
}
/// <summary>
/// Gets the first element's value in the queue and removes it
/// </summary>
/// <returns> The element's value or -1 if the queue is empty</returns>
public int Dequeue()
{
lock (QueueLock)
{
int value;
if (head == -1)
{
value = -1;
}
else
{
value = queue[head];
queue[head] = 0;
if (head == tail)
head = tail = -1;
else
if (head == length - 1)
head = 0;
else
head++;
}
return value;
}
}
/// <summary>
/// Gets a formatted string of the queue elements
/// </summary>
/// <returns>Queue elements</returns>
public string ViewQueueElements()
{
lock (QueueLock)
{
int i;
string result = " Queue Emelemnts: ";
if (head == -1)
{
result = " No Elements Found !";
}
else
{
if (tail < head)
{
//for(i = head; i <= size - 1; i++)
for (i = 0; i <= length - 1; i++)
result += queue[i] + " ";
}
else
//for(i = head; i <= tail; i++)
for (i = 0; i <= tail; i++)
result += queue[i] + " ";
}
return result + "\n";
}
}
}
|
9: The ‘using’ keyword
Write some code that highlights the two primary uses of the ‘using’ keyword.
What are the benefits?
1) using System;
Enables accessing the namespace public member for reusability.
2) using (SqlConnection connection = new SqlConnection(""))
{
SqlCommand command = connection.CreateCommand();
command.CommandText = "sp_GetData";
command.CommandType = CommandType.StoredProcedure;
connection.Open();
object result = command.ExecuteScalar();
}
Provides a convenient syntax that ensures the correct use of IDisposable objects.
|
10: Classes and Interfaces
Explain briefly the difference between sealed classes; classes; abstract classes and interfaces.
Classes: are strongly typed types that can be inherited and initiated, it can implement multiple interfaces but it inherits only one class type even if this class is an abstract class.
Sealed Classes: a type of classes that does not support inheritance, so sealed class can’t be inherited.
Abstract Classes: a type of classes that does not support objects initiations, so abstract classes can’t be initiated.
Interfaces: are not types, does not contain code implementations, contains signatures only for methods/properties and variables, can’t have access modifiers, can’t be initiated but can be implemented by classes as mentioned.
|
11: Implement a Singleton
Show a quick implementation of a singleton. What are the benefits? What are the problems?
public sealed class Singleton
{
static Singleton instance=null;
static readonly object padlock = new object();
Singleton()
{
}
public static Singleton Instance
{
get
{
lock (padlock)
{
if (instance==null)
{
instance = new Singleton();
}
return instance;
}
}
}
|
