Thread: divide by zero

Hello everyone,


I have verified that the result of 100/0 will not occur any exception, and it will be infinite.

Does it mean there is no exceptions like divide by zero in C#?


thanks in advance,
George

Thanks Mats and Magos,


I have tried as well. Seems the conclusion is, int/decimal will occur divide by zero exception, but float/double will not?

Originally Posted by Magos

100 / 0 throws a DivideByZero exception
100.0 / 0.0 does not throw an exception and the result will be Inf

regards,
George

Thats what happens when Microsoft invents a language. Though jabbing ms aside, they probably did that to lower instances of run-time errors. Though, that is one you'd want to know about, as the developer.

Thanks master5001,


Agree with my points in post #4? :-)

Originally Posted by master5001

Thats what happens when Microsoft invents a language. Though jabbing ms aside, they probably did that to lower instances of run-time errors. Though, that is one you'd want to know about, as the developer.

regards,
George

Yeah I do agree with you. I just couldn't imagine how a company that develops software would consider that a useful characteristic for other developers. Who knows. Good find though. I don't use C# as often as C/C++/VB, but I will keep that in mind. Though now I am going to have to do some tests with VB, chances are it does the same.

Thanks for your clarification, master5001!

Originally Posted by master5001

Yeah I do agree with you. I just couldn't imagine how a company that develops software would consider that a useful characteristic for other developers. Who knows. Good find though. I don't use C# as often as C/C++/VB, but I will keep that in mind. Though now I am going to have to do some tests with VB, chances are it does the same.

regards,
George

George2 could merely be looking for consistency in the responses received for a given post. Boards systems have come along way with the growing knowledgability of a more informed programming society, but we still have a ways to go. Allot of times you have to, still yet, piece mill a solution together and inevitably debug the holy hell out of it to get it up to snuff, but it is getting better all the time because of members like you all.

The divide by zero appears to be a .Net Framework problem in scope. This scenario involves all .Net languages to include C# and VB.Net to name a short few. The VS .Net executables and .dll's are assembly sets that act as 'assembly instructions' that are parsed and then sent to the .Net JIT compiler for creation.

Basically a .Net assembly acts as a Make and Linker file all in one and it is with this all in one file that the JIT compiles and links your system into bytecode and dynamically stored into memory for operations.

The divide by zero will have to be handled with managed code from within your system's internal code with a specially designed try - catch method as previously stated. The reasoning behind the managed handling was that the .Net Framework has to be a common interface for any language that wants to use it and not all programming languages handle divide by zero equally. This method of handling the divide by zero fault eliminates allot of overiding and system clashes for the time being.

I personally think that a nominal divide by zero try-catch error handling system should be present, if it isn't already and we are merely overlooking it somehow, and to avoid system clashes between languages you must declare the default as being used for DB0 or you must define it yourself with managed code. This would eliminate allot of confusion.

Thanks TheRaven,


1.

Originally Posted by TheRaven

Basically a .Net assembly acts as a Make and Linker file all in one and it is with this all in one file that the JIT compiles and links your system into bytecode and dynamically stored into memory for operations.

I am interested why you call a .Net assembly "a Make and Linker file all in one"? :-)

2.

Originally Posted by TheRaven

I personally think that a nominal divide by zero try-catch error handling system should be present, if it isn't already and we are merely overlooking it somehow, and to avoid system clashes between languages you must declare the default as being used for DB0 or you must define it yourself with managed code. This would eliminate allot of confusion.

What means DB0?


regards,
George

Thanks Mats and Cat,


Any comments to my question item 1 in post #12?

Originally Posted by Cat

That's because floating-point numbers have special values for Infinity and NaN (Not a Number). It just sets the result to Inf if there is division by zero (though I'd argue from a mathematical point of view, NaN would be more appropriate as the result of such a division is undefined).

regards,
George