It's always a hassle to define our 2D Geometry library during a contest. Is there a way to make our computational geometry lives easier in any way? Fortunately for us, there is, at least in C++, using complex numbers.

**Complex numbers** are of the form a + bi, where a is the real part and b imaginary. Thus, we can let a be the x-coordinate and b be the y-coordinate. Whelp, complex numbers can be represented as 2D vectors! Therefore, we can use complex numbers to define a point instead of defining the class ourselves. You can look at std::complex reference here.

#### Defining our point class

We can define our point class by typing `typedef complex<double> point;`

at the start of our program. To access our x- and y-coordinates, we can macro the `real()`

and `imag()`

functions by using `#define`

. Of course, don't forget to `#include <complex>`

before anything.

```
#include <iostream>
#include <complex>
using namespace std;
// define x, y as real(), imag()
typedef complex<double> point;
#define x real()
#define y imag()
// sample program
int main() {
point a = 2;
point b(3, 7);
cout << a << ' ' << b << endl; // (2, 0) (3, 7)
cout << a + b << endl; // (5, 7)
}
```

Oh goodie! We can use `std:cout`

for debugging! We can also add points as vectors without having to define `operator+`

. Nifty. And apparently, we can overall add points, subtract points, do scalar multiplication **without defining any operator**. Very nifty indeed.

#### Example

```
point a(3, 2), b(2, -7);
// vector addition and subtraction
cout << a + b << endl; // (5,-5)
cout << a - b << endl; // (1,9)
// scalar multiplication
cout << 3.0 * a << endl; // (9,6)
cout << a / 5.0 << endl; // (0.6,0.4)
```

#### Functions using std::complex

What else can we do with complex numbers? Well, there's a lot that is really easy to code.

Vector addition:

`a + b`

Scalar multiplication:

`r * a`

Dot product:

`(conj(a) * b).x`

Cross product:

`(conj(a) * b).y`

**notice**:*conj(a) * b = (ax*bx + ay*by) + i (ax*by — ay*bx)*Squared distance:

`norm(a - b)`

Euclidean distance:

`abs(a - b)`

Angle of elevation:

`arg(b - a)`

Slope of line (a, b):

`tan(arg(b - a))`

Polar to cartesian:

`polar(r, theta)`

Cartesian to polar:

`point(abs(p), arg(p))`

Rotation about the origin:

`a * polar(1.0, theta)`

Rotation about pivot p:

`(a-p) * polar(1.0, theta) + p`

**UPD**: added more useful functionsAngle ABC:

`abs(remainder(arg(a-b) - arg(c-b), 2.0 * M_PI))`

remainder normalizes the angle to be between [-PI, PI]. Thus, we can get the positive non-reflex angle by taking its abs value.Project p onto vector v:

`v * dot(p, v) / norm(v);`

Project p onto line (a, b):

`a + (b - a) * dot(p - a, b - a) / norm(b - a)`

Reflect p across line (a, b):

`a + conj((p - a) / (b - a)) * (b - a)`

Intersection of line (a, b) and (p, q):

```
point intersection(point a, point b, point p, point q) {
double c1 = cross(p - a, b - a), c2 = cross(q - a, b - a);
return (c1 * q - c2 * p) / (c1 - c2); // undefined if parallel
}
```

### Drawbacks

Using std::complex is very advantageous, but it has one disadvantage: you can't use `std::cin`

or `scanf`

. Also, if we macro x and y, we can't use them as variables. But that's rather minor, don't you think?

EDIT: Credits to Zlobober for pointing out that `std::complex`

has issues with integral data types. The library will work for simple arithmetic like vector addition and such, but not for `polar`

or `abs`

. It will compile but there will be some errors in correctness! The tip then is to rely on the library only if you're using floating point data all throughout.

I've used std::complex as a geometry primitive before, but there is a serious disatvantage: by using it, you can't perform operations in integral data types. I always prefer using my own integral vectors when the task allows it (also some tasks simply can't be solved in doubles).

What you mean by

`"you can't perform operations in integral data types"`

? You can use`typedef complex<long long> point;`

and every operation which should work with integral data types will work.According to C++ standard, instantiating complex with any data type other than standard float-point types is unspecified. This means that although it may even be compiled, it may work not as you expect it to work.

Some links related to this issue:

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3337.pdf (section 26.4.2)

http://stackoverflow.com/questions/11108587/why-does-abscomplexint-always-return-zero

http://stackoverflow.com/questions/11108743/why-does-c-mandate-that-complex-only-be-instantiated-for-float-double-or-lon

I believe that using unspecified behaviour that depends much on compiler and platform is a bad idea.

Thank you, I didn't know that. I have used

`complex<long long>`

a lot so I guess it should work in expected way with most of the modern compilers (you shouldn't use complex abs with integers anyway). I will continue using`complex<long long>`

but this is a good reason to not use it.A good article on TopCoder about geometry with complex numbers

The intersection part is interesting. Thanks for sharing!

Auto comment: topic has been updated by Hikari9 (previous revision, new revision, compare).Auto comment: topic has been updated by Hikari9 (previous revision, new revision, compare).Really nice reference list! :)

To use cin, we just need to overload the operator. I don't see a problem with this in competitions:

I think

`p.real(value)`

and`p.imag(value)`

only works for C++11, but yeah, most competitions have C++11 compilers anyway so this is a good suggestion.Just for reference,

`polar(r, theta)`

is equal to`r * exp(point(0, theta))`

, which is cool because it obeys the Euler's identity.どもうありがとう

I don't get this one... What is it?

Slope of line b/w points a and b.

The arctan of the slope of the line connecting

aandb. In other words, the angle that the line connectingaandbforms with thex-axis in positive direction.Suggestion: Instead of using

`#define x real()`

and`#define y imag()`

it's easier to use`#define x() real()`

and`#define y() imag()`

so that you can use`x()`

and`y()`

as getter methods without having to remember to always avoid using the variables`x`

and`y`

in other contexts, especially if you include this code in a template.The problem with geometry isn't in such technical details, it's the thousands of special cases you have to watch out for :D.