make all
An alternate version exists that fixes a bug.
The current status of this entry is:
STATUS: known bug - please help us fix
For more detailed information see 1992 albert bugs.
./albert number
./try.sh
An alternate version of this entry, albert.alt.c, is provided. Leo Broukhis, before he was an IOCCC judge, sent the IOCCC judges this Email message:
From: leo _at_ zycad -dot- com (Leo Broukhis)
Date: Tue, 30 Jan 96 17:37:51 PST
To: judges _at_ toad -dot- com
Subject: IOCCC 1992 - a bug
Dear Judges,
albert.c (even in its fixed form) still has a bug. Although I don't
remember the number that exposed the bug (afair, resulting in coredump)
in albert.orig.c that has been fixed in albert.c,
I've found a number exposing another bug: 10000000001 (that's 9 0's).
Both albert and albert.orig loop without printing anything, although
the first factor is 101 and is usually found in an instant.
The albert.alt.c file is the fixed file, whereas the albert.c is the file before applying Leo Broukhis’ fix.
To compile this alternate version:
make alt
Use albert.alt
as you would albert
above.
./try.alt.sh
We were impressed with the speed at which it was able to factor arbitrarily large numbers consisting of factors that fit into a long.
The Obfuscated version of the Horst algorithm.
This program will factor unlimited length numbers and print the factors in ascending order. Numbers of one digit (e.g. 8) are rejected without notice.
It quits as soon as there is at most one factor left, but that factor will not be shown. It accomplishes this efficiently, without resorting to division or multiplication, until the candidate factor no longer fits in a signed long.
The nicest way is to rename the program into e.g. 4294967297 if you want to factor Fermat’s 4th number. Then just run it.
Or you may type ./albert <some-number>
A nice one is also (30 ones):
./albert 111111111111111111111111111111
Apart from the foregoing there are no special execution instructions.
To customize the program into a factorizer of a fixed number, use
cc albert.c -o 4294967297
or some such.
There are no data files used, and it is not possible to feed input
via stdin
.
I think this program is a nice example of algorithmic obfuscation. Several times two similar algorithms are merged into one. Then you need quite some tricks to get it running, such as long jumps through recursive subroutines. I felt like a sword smith, welding the sword very long, folding it again to the proper length, keep on hammering till it is tight, then fold again. Always keeping it at the proper red hot temperature, but not too hot lest the hardness fades.
The strict naming conventions for subroutines did not make things much clearer after all, but it was not supposed to.
I would like to draw attention to the robustness of the program with respect to error handling and the nice stopping criterion. The aesthetic appeal of some lines is at the expense of clearness, I apologize.
Running the program through the C-beautifier reveals nothing, it will only destroy some of the lay out. Running the program through lint shows the usual remarks for a K&R program. Defeating this through casts does not make a program cleaner in my opinion.
Here are some hints, but they may not be too helpful: