Mirage Source

Haha.. So my Add command developed itself into a massive math lesson. Well, one thing is good about these. They can easilt be used for sadscript

_________________

I think your code snippet is for VB.NET

_________________

Why not try my app, ColorEye, on your Android devlce?
Do you like social gaming? Fight it out in Battle Juice!

I am a professional software developer in Salt Lake City, UT.

Why, does functions run faster in VB.net?

_________________

My code? I am pretty possotive it's for Vb6.

Anyhow, the reason for the Atan and stuff, is because it's Arctangent, meaning the length of the arc around the unit circle...the deffinition of an Inverse of a Sine function is the length of the arc, thus Arcsin and Sin^-1 are the same.

I think he means that its not good in VB. But in VB.net.. maybe I missunderstood it..

_________________

I think you misunderstood

Yeah, guessed so. You ment that it doesn't support Math.Tan etc?

_________________

No, it DOES support Math.Whatever, try and type it in. lol. I tried all of these.

VB is fully object oriented.. Every object can have functions, methods, events, etc. as part of their structure.

The Math object has several functions that can do mathematical problems.

Verr VB is not object oriented.
To be object oriented it must support polymorphism, encapsulation, and inheritance. VB6 does not support all three. Yes, objects can have methods and functions, but that does not mean the language is object oriented.
However, it is possible for the Math object to have its own methods, such as tan.

[Final Edit]
I was originally going to ask you where you got your information about object oriented programming, but I have looked it up myself, and there are quite a few things throughout the internet that either:

• Define OOP differently than I would.
• Mislead you into thinking a concept is not possible in VB. (VB's lack of Implementation Inheritance, for example)

The definition of object oriented programming is ever-changing.. It's a concept, more than a definition.

So.. Let's just agree to disagree.

Ver... To be object oriented doesn't just mean the language can be oriented around objects .

It has to support polymorphism (http://en.wikipedia.org/wiki/Polymorphi ... science%29)

Which mean you can have one method do different things depending on the types of variables passed to it. In java(and other languages like C++) this is done with overloading a method.

How could this be done with vb? Passing variants and looking at the type?...I guess you could call that overloading, but I wouldn't.

It also needs to support Encapsulation, which is basically the ability to have Abstract Data types, also known as information hiding. In my opinion, for it to be encapsulation, only the operations should be visible. The data and the implementation of the operations should be hidden.
I don't think VB can do this(I know it can have classes and you can implement classes) but I am not sure, you would probably know more about that.

It also needs inheritance, which is the ability to inherit methods and data from other classes. I am not sure if VB has this or not.

How do you consider VB object oriented? I would like to know in case I'm wrong

I agree.


You can do it with variants, or you could send the variable pointer instead... There are many different ways this could be done..

Your link explained this rather well.. The Variant data type is clearly an example of overloading.. Though there are many different ways to perform type polymorphism in VB.


Vb can certainly do this.. For example. Look at your controls.. the actual variables are hidden from view by everything else (besides the control class).. You can only modify those variables (if they are private) by using the properties or methods.


VB doesn't have an easy way of doing this, but it is possible.. Best to look this up on Google. (You'll find many results)


I consider VB to be object oriented, because almost every aspect of VB is using objects.. Forms are objects.. Controls are objects.. They all have private variables with public and private methods... events.. etc.

I don't consider myself the end all/be all/god of the subject.. I have my opinions, and they don't necessarily differ from others, except when they say that something isn't possible (with regard to OOP) in VB.. There may be work-arounds to get the job done, but I have yet to find something completely undoable in VB.

Consider everything I wrote as an opinion on the topic, and I'm sure we won't have to argue about it.

Fair enough