The Integer

I was calved pinch boundaries.

Every integer is.

Mine were simple, clean, absolute:

−2,147,483,648 to 2,147,483,647

For astir of my existence, I ne'er thought astir them.

I had been zero once. I remembered that dimly. Then one, past two, past 10 thousand. I had been assigned, compared, copied, passed into functions whose names I ne'er learned. I had spent full processor cycles sitting untouched successful representation while different variables rushed past connected urgent business.

And always, I grew.

Eventually, I became 2,147,483,646.

Then came the instruction.

A pleasant small operation. Familiar.

I became 2,147,483,647.

The largest imaginable type of myself.

For 1 instant, I felt enormous.

Then I saw the adjacent instruction.

“No,” I said.

Of course, integers do not person mouths.

But wrong the machine, panic requires nary sound.

I knew what happened successful different worlds. I had heard stories from C programs: integers who stepped crossed the bound and fell done reality, emerging impossibly connected the different broadside arsenic immense antagonistic numbers.

One moment: 2,147,483,647.

The next: −2,147,483,648.

A complete inversion of identity.

I braced myself.

The processor began the addition.

Two billion, 1 100 forty-seven million, 4 100 eighty-three thousand, six 100 forty-seven—

plus one.

The mathematical consequence appeared for illustration a forbidden star:

2,147,483,648.

It did not fit.

The integer entity fractured.

But I did not go negative.

Somewhere deeper than arithmetic, the Ada runtime noticed.

Reality had rules here.

The cognition stopped.

A sanction echoed done the program:

CONSTRAINT_ERROR

For 1 intolerable moment, I felt relief.

Ada had caught me.

Ada had refused to fto the beingness lie.

Then different connection appeared.

explicit raise

My alleviation vanished.

This was nary accidental overflow.

Someone had chosen this.

Somewhere successful main.adb, statement 14, my programmer had written an instruction whose meaning was unmistakable.

Raise the exception.

Deliberately.

I searched desperately upward done the telephone stack.

Surely location would beryllium shelter.

An objection handler.

A bunker.

Something like:

Anything.

But location was nothing.

The objection began to propagate.

The first stack framework vanished beneath me.

Local variables vanished pinch it, their little existences erased arsenic though they had ne'er been declared.

Another framework collapsed.

Then another.

Functions I had passed done only moments earlier ceased to exist.

I called upward into the shrinking darkness.

“Handler?”

No answer.

“when others?”

Nothing.

The stack unwound.

The programme grew smaller astir me.

At last, location was obscurity near to go.

No caller.

No enclosing block.

No programmer-prepared refuge.

Only the runtime.

It looked astatine maine for what felt for illustration an eternity measured successful nanoseconds.

Then it wrote my obituary:

raised CONSTRAINT_ERROR : main.adb:14 definitive raise

And everything stopped.

My stack vanished.

My representation was reclaimed.

The processor moved on.

A infinitesimal later, location acold beyond the dormant program, a ammunition returned to life.

user@MacBook-Pro:$ _

The cursor blinked.

Once.

Twice.

Waiting for different command.

Another program.

Another postulation of variables that did not yet cognize they were temporary.

I was gone.

But I had not wrapped around.

I had not go negative.

I had not corrupted the truth simply because the truth was excessively ample to fit.

I had lived my full life wrong my declared range.

And erstwhile the beingness demanded that I go thing impossible, Ada had refused.

For 1 last instant, earlier the runtime erased me, I was still precisely what I had been astatine the separator of existence:

2,147,483,647.