From 5d9f9f6aec9912b6e962c05434c2dce2835933ea Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Wed, 8 Feb 2023 05:57:29 -0800 Subject: [PATCH] Fix 1992/albert README The README.md had an email to the judges from Leo (prior to being a judge, presumably) which means that the index file would not end up with information about the entry. The old contents of the README.md were copied to albert.bug.md though perhaps it should not be a markdown file. The name was arbitrarily selected and a better name could certainly be contrived. --- 1992/albert/README.md | 99 ++++++++++++++++++++++++++++++++------- 1992/albert/albert.bug.md | 22 +++++++++ 1992/albert/albert.hint | 85 --------------------------------- 3 files changed, 103 insertions(+), 103 deletions(-) create mode 100644 1992/albert/albert.bug.md delete mode 100644 1992/albert/albert.hint diff --git a/1992/albert/README.md b/1992/albert/README.md index 315060ef5..68c0bd2ac 100644 --- a/1992/albert/README.md +++ b/1992/albert/README.md @@ -1,22 +1,85 @@ -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 +Most Useful Program: -Dear Judges, + Albert van der Horst + S P&A R&C + Oranjestraat 8 + 3511 RA UTRECHT + The Netherlands -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. -Unfortunately, the e-mail address in albert.hint is no longer valid, -and neither whois, nor replacing old domain name with a new one according -to the MX records, nor Altavista Web search were successful. +Judges' comments: -...Fortunately, Albert van der Horst did send me an unobfuscated -(but somewhat limited - it doesn't check the number for factors 2, 3, 5, 7) -version of his program. I didn't have a chance to augment its functionality -to the one of the contest entry. + For a canned example: + make albert + albert 1234567890123456789 + + We were impressed with the speed at which it was able to factor + arbitrarily large numbers consisting of factors that fit into + a long. + + +Selected notes from the author: + + 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 "prog " + 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 esthetic 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. + 1. The Horst algorithm is described in the Hobby Computer Club + Newsletter, year 82, part 4, a real Dutch treat. + Assembler, c and Forth version have been around for some years. + 2. Does fractal programming exist after all? + 3. You remember the ToomCook algorithm in Knuth? + It uses iteration instead of recursion and is quite jumpy. + This program shares these disadvantages in a modified form. + 4. The Conversion is to be found in Knuth, not so the Observation. + The Observation: "if it ends in a zero, it is divisible by ten" + +Copyright (c) 1992, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1992/albert/albert.bug.md b/1992/albert/albert.bug.md new file mode 100644 index 000000000..315060ef5 --- /dev/null +++ b/1992/albert/albert.bug.md @@ -0,0 +1,22 @@ +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. + +Unfortunately, the e-mail address in albert.hint is no longer valid, +and neither whois, nor replacing old domain name with a new one according +to the MX records, nor Altavista Web search were successful. + +...Fortunately, Albert van der Horst did send me an unobfuscated +(but somewhat limited - it doesn't check the number for factors 2, 3, 5, 7) +version of his program. I didn't have a chance to augment its functionality +to the one of the contest entry. diff --git a/1992/albert/albert.hint b/1992/albert/albert.hint deleted file mode 100644 index 68c0bd2ac..000000000 --- a/1992/albert/albert.hint +++ /dev/null @@ -1,85 +0,0 @@ -Most Useful Program: - - Albert van der Horst - S P&A R&C - Oranjestraat 8 - 3511 RA UTRECHT - The Netherlands - - -Judges' comments: - - For a canned example: - make albert - albert 1234567890123456789 - - We were impressed with the speed at which it was able to factor - arbitrarily large numbers consisting of factors that fit into - a long. - - -Selected notes from the author: - - 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 "prog " - 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 esthetic 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. - 1. The Horst algorithm is described in the Hobby Computer Club - Newsletter, year 82, part 4, a real Dutch treat. - Assembler, c and Forth version have been around for some years. - 2. Does fractal programming exist after all? - 3. You remember the ToomCook algorithm in Knuth? - It uses iteration instead of recursion and is quite jumpy. - This program shares these disadvantages in a modified form. - 4. The Conversion is to be found in Knuth, not so the Observation. - The Observation: "if it ends in a zero, it is divisible by ten" - -Copyright (c) 1992, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel.