C#

[Serializable]
public sealed class EncodingException : Exception, ISerializable
{
  private int _Offset = 0;
  public int Offset
  { get { return _Offset; } }

  public override string Message
  {
    get
    {
      StringBuilder builder = new StringBuilder(base.Message);
      builder.AppendFormat("Illegal encoding encountered at " +
      "Offset {0}{1}", _Offset, Environment.NewLine);
      
      return builder.ToString();
    }
  }

  // Base Class
  public EncodingException() : base() { }
  public EncodingException(String message) : base(message) { }
  public EncodingException(String message, Exception innerException)
    : base(message, innerException) { }

  public EncodingException(int offset) { _Offset = offset; }

  public EncodingException(string message, int offset)
    : this(message) { _Offset = offset; }

  public EncodingException(int offset, Exception innerException)
    : this("", innerException) { _Offset = offset; }

  public EncodingException(string message, int offset, Exception innerException)
    : this(message, innerException) { _Offset = offset; }
  
  // Serialization
  private EncodingException(SerializationInfo info, StreamingContext context)
    : base(info, context)
  {
    _Offset = info.GetInt32("Offset");
  }

  // Allow callers to access state of this object
  [SecurityPermission(SecurityAction.Demand, SerializationFormatter=true)]
  public override void GetObjectData(SerializationInfo info, StreamingContext context)
  {
    base.GetObjectData(info, context);
    info.AddValue("Offset", _Offset);
  }
}

Luc Pattyn wrote:

So by default you get none...

Jeffrey Walton wrote:

Any ideas why no exceptions are being caught?

short shorty = 32767;           // largest positive short<br />
            int integer = shorty + 1;<br />
            try<br />
            {<br />
                checked                       // force compiler to object<br />
                {<br />
                    shorty = (short)integer;  // try to cram it into a short<br />
                }<br />
            }<br />
            catch ( OverflowException e )<br />
            {<br />
                //"Arithmetic operation resulted in an overflow."<br />
                Console.WriteLine (e.Message);<br />
            }

int Eaten = 0;<br />
try<br />
{<br />
   throw new EncodingException("this is encoding exception");<br />
}<br />
catch (EncodingException ex)<br />
{<br />
  // Eat this exception. We are only testing if the<br />
  // the Bit String or Octet String can be parsed.<br />
  // Since we are here, it apparently cannot be parsed.<br />
  // Return -1 to screw up the math. The bad math will be<br />
  // recognised in the caller.<br />
  Debug.Print(ex.Message);<br />
<br />
  return -1;<br />
}<br />
<br />
catch (OverflowException ex)<br />
{<br />
  Debug.Print(ex.Message);<br />
<br />
  return -1;<br />
}<br />
<br />
catch( Exception ex)<br />
{<br />
  Debug.Print(ex.Message);<br />
<br />
  return -1;<br />
}<br />

Michael Sync wrote:

int Eaten = 0;
try
{
  throw new EncodingException("this is encoding exception");
}
  catch (EncodingException ex)
  ...
}

Another advantage of exceptions is that they do not have to be caught or detected in the place they occur; any code in the thread's call stack can handle a thrown exception.

Jeffrey Walton wrote:

Are you staing that the exception can only be caught in the function that generates it?

private int MyMethod(){<br />
  throw new EncodingException("this is encoding exception");  <br />
}<br />
int Eaten = 0;<br />
try<br />
{<br />
  Eaten = MyMethod();<br />
}

Michael Sync wrote:

What is your interest??

Michael Sync wrote:

Every body can't be a software engineer, programmer or developer...

Jeffrey Walton wrote:

I don't know why I tried this language.

Jeffrey Walton wrote:

I'm acutally a Security Engineer. I program to supplement my primary skills. I usually program in C++. See Artciles[^]

Jeffrey Walton wrote:

As for the ranting of the language, it disgusts me when behavior is not documented and bugs exists.

Jeffrey Walton wrote:

he work around for this bug (I just found it) is to prepend the namespace to the EncodingException.

Michael Sync wrote:

You should copy the permalink from the threads..

Michael Sync wrote:

Can you share us more about this bug that you just found?

Jeffrey Walton wrote:

As for the ranting of the language, it disgusts me when behavior is not documented and bugs exists. The work around for this bug (I just found it) is to prepend the namespace to the EncodingException. Where the hell is that documented.

alainlyehongloon wrote:

the tutorial

omegazafer wrote:

I want to send these the members of sayilar array to sayilar2 array but one member can be sent to sayilar2 array only one time. For example, 5 is repeated two times in sayilar array but sending to sayilar2 array it must be only one time.