Infinite Compression Explained

Because most of you don't read my blog,(i don't read random blogs as well) and have so much questions about what i'm doing with my programs, i'll write it here:
All of the programs(about 6 developed so far) despite wildly varying routines are targeted to generate large integers.
These integers are not files. Following transformations occurs:
encode
1.file is converted to large integer X(arbitrary length).
2.X multiplied by some scale factor e.g. 10e1000 to get a lower bound
2.(X+1)by some scale factor e.g. 10e1000 to get an uppper bound
3.a search is performed for finding numbers inside that range which are easy to represent via formula.
4.if number(s) found its saved to a file.
decode:
1.a formula is supplied with number(s) and filesize
2.the formula generates an integer/float, which is then divided by scale factor(e.g. 10e1000).
3.the first filesize bytes are then written to output.

the proces isn't perfected yet, because the formulas currently used in my programs either too slow to search or cuttoff at float precision(for non-integer parameters)
________________________________________________
http://xs135.xs.to/xs135/09042/av922.jpg
orbis terrarum delenda est

>>39
You don't need any "wherewithal" to prove that this can't possibly work.

It was proven a decades ago (and it's an obvious, utterly trivial proof), and the fact that /prog/ gets trolled so easily is really disheartening.

Data compression is always one of the areas that attracts the most stupidity for some reason. And /prog/ is attracted to the low hanging fruit of proving obviously retarded stuff wrong.

You fags are sure getting trolled, and you deserve every bit of it. Shame that /prog/ gets ruined in the meantime, for I can barely stand to look at this faggotry now.