Some help!!!!

[Saimadhav]

1.How do I use the bit wise operator?
2. I have tried this code

#include<iostream>
#include<conio.h>
using namespace std;
main()
{
      int a,b;
      cout<<"Enter a number";
      cin>>a;
      b=a^a;
      cout<<a<<" raised to "<<a<<" is "<<b;
      getch();
      }

I use Dev-C++ Compiler.
The above code compiles and the output is like this
Enter a number 5
5 raised to 5 is 0(wrong!!!!!)

How do I raise a number to itself ?

[CornedBee]

2. Use pow() from <math.h> (or std::pow() from <cmath>).
^ is bitwise XOR.

1. There is no bit wise operator. There's bitwise AND, bitwise OR and bitwise XOR, and any tutorial can tell you how to use them. There's also left and right bitshift.

[matsp]

There is no "raised to" operator in C. There is a "pow" function that takes two floating point values.

Bitwise operators have been discussed many times on the forum, so I suggest you do a Search or look at the FAQ/Tutorial sections of the site.

^ is a bitwise operator, representing the "exclusive or" function, and 5 ^ 5 is indeed zero.

If you still have SPECIFIC questions, please feel free to ask for further details.

--
Mats

[Elysia]

This code should not compile. Main must return int, always. No return type is an error in C++.
And I'd also recommend getting rid of the Dev-c++ IDE because it screws up indentation something horribly.
Here's a list of other free IDEs: http://cpwiki.sf.net/IDE

[master5001]

I never had any of the issues with Dev-C++ that people are always seeming to have nowadays. Though its quite an old piece of software, I do not know how come its still in such wide-spread use.

[Elysia]

It has come to my attention that by default, it creates unwanted indentation.
For example, as above, it tends to do

int main()
{
    // bla bla bla
    }

Plus it's frustrating that it simply can't put the indentation level correctly many, many times. The best IDE that in my experience does this correctly and good is Visual Studio (Code::Blocks had some issues, too. I don't know if some settings can change that.)

[master5001]

I don't like how VC tries to change my switch case statements or how it screws up my indentation when I write classes the way I like

Example:

class Oval :
  public virtual shape,
  public virtual drawable,
  public conical
{

};

But that is a very quick backspace. Though its one more backspace than I think I should have to press.

It has come to my attention that by default, it creates unwanted indentation.

That is very poor on behalf of Dev-C++. Again I ask why its even still so widely used. It hasn't had a new version in nearly a decade.

[Elysia]

Wait, how does VC screw up and how did Dev-C++ screw up? I'm sorry, your post didn't seem very clear (it seemed to mix the two together?).
I know VC isn't perfect either (tends to so some things I don't like), but overall, in my opinion, it's better than other IDEs.

[master5001]

Ok there we go. Sorry about that. Run-on thoughts there -_- Just re-read the post now.

I agree with your thoughts on MSVC. The overall impressions of it to me are that though it does a few annoying things, those annoying things are easily fixed.

[Elysia]

Ah, it's much clearer now.
So it creates an extra tab or indentation when you write classes (deriving from other classes), is that it?
And I also suppose you're not entirely happy about how it puts the cases in switches at the same level as the { and } (I don't like it)?

[master5001]

Yeah those are my only real gripes. But to be honest, since I use MSVC++ a lot I am so used to fixing its indenting without even thinking about it, that the issue is mostly trivial.

[Elysia]

I see, I see. Very informative of you. Thank you.
I have a couple of gripes myself.
Everything beginning with "#" is automatically moved to no indentation level.
Cases are on the same level as the switch keyword itself.
VS fails epically when splitting long lines into multiple lines with ( and ) here and there (like I did with cpjust's code in a post). Although I can't say I blame the IDE for it. Must be difficult to know when to choose a different rule. I have to manually indent those.
...And that's all I can think of right now.

[laserlight]

Everything beginning with "#" is automatically moved to no indentation level.

That does make sense though, since macros do not obey scope.

Cases are on the same level as the switch keyword itself.

This is one of the things I like about Visual Studio
The reason is that it seems more consistent when I replace an if/else chain with a switch.

[master5001]

Everything beginning with "#" is automatically moved to no indentation level.

Oh dear lord, yes! That is amazingly irritating. There are a few other issues that have come up periodically. But there are more. Once you get used to it doing something one way, and needing to immediately undo what it did, it becomes second nature and harder to remember which things annoy you since you are so used to just automatically fixing them.

[Elysia]

That does make sense though, since macros do not obey scope.

They don't, generally, but if you want to nest them, you don't want them all to end up on the same indentation level...
But Visual Studio fixes the indentation level each time you hit enter, just typing # destroys that. So it becomes a chore to do things like:

#if x
    #if y
        ...

This is one of the things I like about Visual Studio
The reason is that it seems more consistent when I replace an if/else chain with a switch.

Can't actually see how you like that

Oh dear lord, yes! That is amazingly irritating. There are a few other issues that have come up periodically. But there are more. Once you get used to it doing something one way, and needing to immediately undo what it did, it becomes second nature and harder to remember which things annoy you since you are so used to just automatically fixing them.

Indeed. It does tend to become second nature...