Rename wrongly named author/winner handles
There were many files renamed in this commit and I hope I got all the references to the old names changed to the new names. To explain this commit there were some older entries that had the wrong directory name: not the surname but something else. Very possibly there are other directories that need to be renamed and I am actually aware of one right now but since it's in 2005 (which is close to being worked on) I am not changing that now but just noting it: 2005/anon should be changed to 2005/anonymous (unless there's a very good reason I am unaware of). But like I said since 2005 will be worked on soon I have not touched it. The Makefiles, .gitignore, the all/summary.txt, years.html and winners.html files as well as the directories and the files under the renamed directories have all been updated. This is a rather big update and it might be that there are conflicts. If so I will fix them. I will have to update 2005/anon later on to try and prevent this from happening but very possibly there will be conflicts here. It's also possible I missed some changes in years.html and/or winners.html and/or summary/all.txt but I think I got them all. These should be verified later on.
This commit is contained in:
Cody Boone Ferguson committed
1 parent
9e540136d1
commit
ad04d21fda
52 files changed
+163
-162
No files matched your search
+1
-1
@@ -1,5 +1,5 @@
|
||||
ant/ant
|
||||
cmills/cmills
|
||||
mills/mills
|
||||
dgibson/data.name
|
||||
dgibson/data.name2
|
||||
dgibson/life.d
|
||||
|
||||
+1
-1
@@ -53,7 +53,7 @@ include ../var.mk
|
||||
# IOCCC winners
|
||||
###############
|
||||
#
|
||||
WINNERS= ant cmills dgibson ejb jonth leo lmfjyh plummer rince schnitzi vanb
|
||||
WINNERS= dgibson ejb howe jonth leo lmfjyh mills plummer rince schnitzi vanb
|
||||
|
||||
YEAR= 1993
|
||||
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
cmills
|
||||
@@ -1,3 +1,4 @@
|
||||
ag
|
||||
ag.txt
|
||||
ant
|
||||
howe
|
||||
@@ -1,6 +1,6 @@
|
||||
#!/usr/bin/env make
|
||||
#
|
||||
# IOCCC 1993 winning entry - ant
|
||||
# IOCCC 1993 winning entry - howe
|
||||
|
||||
################################################################################
|
||||
#
|
||||
@@ -160,7 +160,7 @@ endif
|
||||
# Special flags for this entry
|
||||
##############################
|
||||
#
|
||||
ENTRY= ant
|
||||
ENTRY= howe
|
||||
PROG= ${ENTRY}
|
||||
#
|
||||
OBJ= ${PROG}.o
|
||||
@@ -12,14 +12,14 @@
|
||||
|
||||
### To run
|
||||
|
||||
./ant 'ERE' [file ...]
|
||||
./howe 'ERE' [file ...]
|
||||
|
||||
## Judges' comments
|
||||
|
||||
You may also want to try the author's test suite:
|
||||
make -f ant.test.mk
|
||||
make -f howe.test.mk
|
||||
|
||||
See the author's Posix P1003.2-like documentation file ant.txt
|
||||
See the author's Posix P1003.2-like documentation file howe.txt
|
||||
for more information.
|
||||
|
||||
This program demonstrates that Posix doesn't guarantee readability. :-)
|
||||
File renamed without changes.
@@ -5,28 +5,28 @@
|
||||
#
|
||||
|
||||
SHELL=/bin/sh
|
||||
PRG=./ant
|
||||
PRG=./howe
|
||||
|
||||
all: ant char word anchor literal wild closure option branch sub class
|
||||
all: howe char word anchor literal wild closure option branch sub class
|
||||
|
||||
#
|
||||
# Built the entry
|
||||
#
|
||||
ant: Makefile
|
||||
make -f Makefile ant
|
||||
howe: Makefile
|
||||
make -f Makefile howe
|
||||
|
||||
#
|
||||
# Test simple text patterns without the use of meta characters.
|
||||
#
|
||||
|
||||
empty:
|
||||
$(PRG) '' ant.test.mk
|
||||
$(PRG) '' howe.test.mk
|
||||
|
||||
char:
|
||||
$(PRG) 'q' ant.test.mk
|
||||
$(PRG) 'q' howe.test.mk
|
||||
|
||||
word:
|
||||
$(PRG) 'simple' ant.test.mk
|
||||
$(PRG) 'simple' howe.test.mk
|
||||
|
||||
#
|
||||
# Test meta characters.
|
||||
@@ -35,28 +35,28 @@ word:
|
||||
anchor: anchor1 anchor2 anchor3 anchor4 anchor5
|
||||
|
||||
anchor1:
|
||||
$(PRG) '^anchor1' ant.test.mk
|
||||
$(PRG) '^anchor1' howe.test.mk
|
||||
|
||||
anchor2:
|
||||
$(PRG) 'Grep$$' ant.test.mk
|
||||
$(PRG) 'Grep$$' howe.test.mk
|
||||
|
||||
#
|
||||
# Find all empty lines.
|
||||
#
|
||||
anchor3:
|
||||
$(PRG) '^$$' ant.test.mk
|
||||
$(PRG) '^$$' howe.test.mk
|
||||
|
||||
#
|
||||
# This is valid but will never match.
|
||||
#
|
||||
anchor4:
|
||||
-$(PRG) 'x^a' ant.test.mk
|
||||
-$(PRG) 'x^a' howe.test.mk
|
||||
|
||||
#
|
||||
# This is valid but will never match.
|
||||
#
|
||||
anchor5:
|
||||
-$(PRG) 'mk$$x' ant.test.mk
|
||||
-$(PRG) 'mk$$x' howe.test.mk
|
||||
|
||||
literal: literal1 literal2
|
||||
|
||||
@@ -64,13 +64,13 @@ literal: literal1 literal2
|
||||
# Every line with a dollar-sign.
|
||||
#
|
||||
literal1:
|
||||
$(PRG) '\$$' ant.test.mk
|
||||
$(PRG) '\$$' howe.test.mk
|
||||
|
||||
#
|
||||
# Every line with a backslash.
|
||||
#
|
||||
literal2:
|
||||
$(PRG) '\\' ant.test.mk
|
||||
$(PRG) '\\' howe.test.mk
|
||||
|
||||
#
|
||||
# wild #1#
|
||||
@@ -78,7 +78,7 @@ literal2:
|
||||
# wild #%#
|
||||
#
|
||||
wild:
|
||||
$(PRG) '#.#' ant.test.mk
|
||||
$(PRG) '#.#' howe.test.mk
|
||||
|
||||
#
|
||||
# closure !!
|
||||
@@ -86,7 +86,7 @@ wild:
|
||||
# closure !xxxxxx!
|
||||
#
|
||||
closure:
|
||||
$(PRG) 'closure !x*!' ant.test.mk
|
||||
$(PRG) 'closure !x*!' howe.test.mk
|
||||
|
||||
#
|
||||
# option ++
|
||||
@@ -98,45 +98,45 @@ closure:
|
||||
option: option1 option2
|
||||
|
||||
option1:
|
||||
$(PRG) '+b?+' ant.test.mk
|
||||
$(PRG) '+b?+' howe.test.mk
|
||||
|
||||
option2:
|
||||
$(PRG) '+.?+' ant.test.mk
|
||||
$(PRG) '+.?+' howe.test.mk
|
||||
|
||||
branch: branch1 branch2 branch3 branch4 branch5 branch6
|
||||
|
||||
branch1:
|
||||
$(PRG) 'q|simple' ant.test.mk
|
||||
$(PRG) 'q|simple' howe.test.mk
|
||||
|
||||
#
|
||||
# This pattern should be the same as '(^all)|(Public)|(Grep$)'.
|
||||
#
|
||||
branch2:
|
||||
$(PRG) '^all|Public|Grep$$' ant.test.mk
|
||||
$(PRG) '^all|Public|Grep$$' howe.test.mk
|
||||
|
||||
#
|
||||
# This pattern should generate the same results as branch2.
|
||||
#
|
||||
branch3:
|
||||
$(PRG) 'Grep$$|^all|Public' ant.test.mk
|
||||
$(PRG) 'Grep$$|^all|Public' howe.test.mk
|
||||
|
||||
#
|
||||
# Null expression between start of pattern and vertical-line.
|
||||
#
|
||||
branch4:
|
||||
$(PRG) '|Grep' ant.test.mk
|
||||
$(PRG) '|Grep' howe.test.mk
|
||||
|
||||
#
|
||||
# Null expression between vertical-line and end of pattern.
|
||||
#
|
||||
branch5:
|
||||
$(PRG) 'Grep|' ant.test.mk
|
||||
$(PRG) 'Grep|' howe.test.mk
|
||||
|
||||
#
|
||||
# Null expression between vertical-line and vertical-line.
|
||||
#
|
||||
branch6:
|
||||
$(PRG) 'all||Grep' ant.test.mk
|
||||
$(PRG) 'all||Grep' howe.test.mk
|
||||
|
||||
#
|
||||
# sub aabcbcbcxx
|
||||
@@ -151,49 +151,49 @@ sub: sub0 sub1 sub2 sub3 sub4 sub5 lparen1 lparen2 rparen1 rparen2
|
||||
# Null sub-expressions.
|
||||
#
|
||||
sub0:
|
||||
$(PRG) 's()u()b()' ant.test.mk
|
||||
$(PRG) 's()u()b()' howe.test.mk
|
||||
|
||||
sub1:
|
||||
$(PRG) '#(1|%)#' ant.test.mk
|
||||
$(PRG) '#(1|%)#' howe.test.mk
|
||||
|
||||
sub2:
|
||||
$(PRG) 'aa((bc)*|g)xx' ant.test.mk
|
||||
$(PRG) 'aa((bc)*|g)xx' howe.test.mk
|
||||
|
||||
#
|
||||
# Null expression between the left-parenthesis and the vertical-line.
|
||||
#
|
||||
sub3:
|
||||
$(PRG) '#(|1)#' ant.test.mk
|
||||
$(PRG) '#(|1)#' howe.test.mk
|
||||
|
||||
#
|
||||
# Null expression between the vertical-line and the right-parenthesis.
|
||||
#
|
||||
sub4:
|
||||
$(PRG) '#(1|)#' ant.test.mk
|
||||
$(PRG) '#(1|)#' howe.test.mk
|
||||
|
||||
#
|
||||
# Null expression between the vertical-line and the right-parenthesis.
|
||||
#
|
||||
sub5:
|
||||
$(PRG) '#(%||1)#' ant.test.mk
|
||||
$(PRG) '#(%||1)#' howe.test.mk
|
||||
|
||||
#
|
||||
# Missing left-parenthesis generates an error.
|
||||
#
|
||||
lparen1:
|
||||
-$(PRG) 'left ( only' ant.test.mk
|
||||
-$(PRG) 'left ( only' howe.test.mk
|
||||
|
||||
lparen2:
|
||||
$(PRG) 'left \( only' ant.test.mk
|
||||
$(PRG) 'left \( only' howe.test.mk
|
||||
|
||||
#
|
||||
# Right-parenthesis without preceding left parenthesis should be a literal.
|
||||
#
|
||||
rparen1:
|
||||
-$(PRG) 'right ) only' ant.test.mk
|
||||
-$(PRG) 'right ) only' howe.test.mk
|
||||
|
||||
rparen2:
|
||||
$(PRG) 'right \) only' ant.test.mk
|
||||
$(PRG) 'right \) only' howe.test.mk
|
||||
|
||||
#
|
||||
# 12345678
|
||||
@@ -215,26 +215,26 @@ rparen2:
|
||||
class: class1 class2 class3 class4 class5 class6 class7 class8
|
||||
|
||||
class1:
|
||||
$(PRG) '=[09]=' ant.test.mk
|
||||
$(PRG) '=[09]=' howe.test.mk
|
||||
|
||||
class2:
|
||||
$(PRG) '=[^09]=' ant.test.mk
|
||||
$(PRG) '=[^09]=' howe.test.mk
|
||||
|
||||
class3:
|
||||
$(PRG) '=[]]=' ant.test.mk
|
||||
$(PRG) '=[]]=' howe.test.mk
|
||||
|
||||
class4:
|
||||
$(PRG) '=[^]]=' ant.test.mk
|
||||
$(PRG) '=[^]]=' howe.test.mk
|
||||
|
||||
class5:
|
||||
$(PRG) '=[0-9]=' ant.test.mk
|
||||
$(PRG) '=[0-9]=' howe.test.mk
|
||||
|
||||
class6:
|
||||
$(PRG) '=[^0-9]=' ant.test.mk
|
||||
$(PRG) '=[^0-9]=' howe.test.mk
|
||||
|
||||
class7:
|
||||
-$(PRG) '=[3-1]=' ant.test.mk
|
||||
-$(PRG) '=[3-1]=' howe.test.mk
|
||||
|
||||
class8:
|
||||
$(PRG) '=[-13]=' ant.test.mk
|
||||
$(PRG) '=[-13]=' howe.test.mk
|
||||
|
||||
@@ -31,7 +31,7 @@ None.
|
||||
4. OPERANDS
|
||||
|
||||
pattern Specify one pattern to be used during the search for
|
||||
input. See Extended Regular Exprssions below on what
|
||||
input. See Extended Regular Expressions below on what
|
||||
constitutes a valid pattern.
|
||||
|
||||
file A pathname of a file to be searched for the pattern.
|
||||
@@ -39,12 +39,12 @@ file A pathname of a file to be searched for the pattern.
|
||||
is dash (-), the standard input shall be used.
|
||||
|
||||
|
||||
5. EXTERNINAL INFLUENCES
|
||||
5. EXTERNAL INFLUENCES
|
||||
|
||||
5.1. STANDARD INPUT
|
||||
|
||||
The standard input shall be used only if no file operands are
|
||||
specifed. See Input Files.
|
||||
specified. See Input Files.
|
||||
|
||||
|
||||
5.2. INPUT FILES
|
||||
@@ -99,7 +99,7 @@ without parentheses would have matched.
|
||||
|
||||
7.1.1.1. ERE ORDINARY CHARACTERS
|
||||
|
||||
An oridinary character is an ERE that matches itself. An ordinary
|
||||
An ordinary character is an ERE that matches itself. An ordinary
|
||||
character is any character in the supported character set, except for
|
||||
the ERE special characters listed in 7.1.1.2. The interpretation of
|
||||
an ordinary character preceded by a backslash (\) is the ordinary
|
||||
@@ -129,7 +129,7 @@ which they have their special meaning are:
|
||||
except when used in a bracket expression.
|
||||
Results are undefined if this character
|
||||
appears first in an ERE, or immediately
|
||||
following a vertial-line, circumflex, or
|
||||
following a vertical-line, circumflex, or
|
||||
left-parenthesis.
|
||||
|
||||
| The vertical-line is special except when used
|
||||
@@ -162,7 +162,7 @@ set of characters represented by the bracket expression.
|
||||
The following rules and definitions apply to bracket expressions:
|
||||
|
||||
1) A bracket expression is either a matching list expression
|
||||
or a nonmatching list expression. It consists of one or more
|
||||
or a non-matching list expression. It consists of one or more
|
||||
characters and/or range expressions. The right-bracket (])
|
||||
shall lose its special meaning and represent itself in a
|
||||
bracket expression if it occurs first in the list [after an
|
||||
@@ -176,7 +176,7 @@ The following rules and definitions apply to bracket expressions:
|
||||
character of the list shall not be the circumflex. For
|
||||
example, [abc] is an ERE that matches any of a, b, or c.
|
||||
|
||||
3) A nonmatching list expression begins with a circumflex (^),
|
||||
3) A non-matching list expression begins with a circumflex (^),
|
||||
and specifies a list that shall match any character except for
|
||||
the expressions represented in the list after the leading
|
||||
circumflex. For example, [^abc] is an ERE that matches any
|
||||
@@ -191,7 +191,7 @@ The following rules and definitions apply to bracket expressions:
|
||||
|
||||
In the following, all examples assume the collation sequence
|
||||
specified for the POSIX Locale (a.k.a ASCII Character Set),
|
||||
unless another collation sequence is sepecifically defined
|
||||
unless another collation sequence is specifically defined
|
||||
by the hardware.
|
||||
|
||||
The starting range point and the ending range point shall be a
|
||||
@@ -208,7 +208,7 @@ The following rules and definitions apply to bracket expressions:
|
||||
an ending range point in a range expression. As examples, the
|
||||
expressions [-ac] and [ac-] are equivalent and match any of
|
||||
the characters a, c, or -; the expressions [^-ac] and [^ac-]
|
||||
are equivalent and match ant character except a, c, -; the
|
||||
are equivalent and match howe character except a, c, -; the
|
||||
expression [%--] matches any of the characters between % and
|
||||
- inclusive; the expression [--@] matches any of the
|
||||
characters between - and @ inclusive; and the expression
|
||||
@@ -228,10 +228,10 @@ characters from EREs matching a single character:
|
||||
example, both the ERE cd and the ERE (cd) are matched by the
|
||||
third and forth character of the string abcdefabcdef.
|
||||
|
||||
2) When an ERE matching a single character, or a concatention of
|
||||
2) When an ERE matching a single character, or a concatenation of
|
||||
EREs enclosed in parentheses is followed by the special
|
||||
character asterisk (*), together with that asterisk it shall
|
||||
match what zero or more consecutive occurences of the ERE
|
||||
match what zero or more consecutive occurrences of the ERE
|
||||
would match. For example, the ERE b*c matches the first
|
||||
character in the string cabbbcde, and the ERE b*cd matches the
|
||||
third through seventh characters in the string
|
||||
@@ -241,7 +241,7 @@ characters from EREs matching a single character:
|
||||
3) When an ERE matching a single character or an ERE enclosed in
|
||||
parentheses is followed by the special character question-mark
|
||||
(?), together with that question mark it shall match what zero
|
||||
or one consecutive occurences of the ERE would match. For
|
||||
or one consecutive occurrences of the ERE would match. For
|
||||
example, the ERE b?c matches the second character in the
|
||||
string acabbbcde.
|
||||
|
||||
@@ -333,7 +333,7 @@ and that ARRAY be set to 256. For Watcom C the command line would be
|
||||
|
||||
The value ARRAY represents the size of the compiled pattern array and
|
||||
the size of the array used to record matched states. The default
|
||||
value choosen should handle most patterns. ARRAY can be overridden on
|
||||
value chosen should handle most patterns. ARRAY can be overridden on
|
||||
the command line with -DARRAY=nn, where 255 < nn < INT_MAX.
|
||||
|
||||
|
||||
@@ -366,7 +366,7 @@ The expression (a*)* compiles but loops forever.
|
||||
There is no check for trailing backslash (\) in the pattern.
|
||||
|
||||
There is no check for unbalanced brackets. Omitting a closing bracket
|
||||
will generate a "Patern too long" error, which is not the real error.
|
||||
will generate a "Pattern too long" error, which is not the real error.
|
||||
|
||||
|
||||
13. NOTICES
|
||||
@@ -0,0 +1 @@
|
||||
mills
|
||||
@@ -1,6 +1,6 @@
|
||||
#!/usr/bin/env make
|
||||
#
|
||||
# IOCCC 1993 winning entry - cmills
|
||||
# IOCCC 1993 winning entry - mills
|
||||
|
||||
################################################################################
|
||||
#
|
||||
@@ -161,7 +161,7 @@ endif
|
||||
# Special flags for this entry
|
||||
##############################
|
||||
#
|
||||
ENTRY= cmills
|
||||
ENTRY= mills
|
||||
PROG= ${ENTRY}
|
||||
#
|
||||
OBJ= ${PROG}.o
|
||||
@@ -14,7 +14,7 @@
|
||||
|
||||
DISPLAY="your_X_server_display"
|
||||
export DISPLAY
|
||||
./cmills [speed] # must be run on an X11 server
|
||||
./mills [speed] # must be run on an X11 server
|
||||
|
||||
where:
|
||||
|
||||
File renamed without changes.
Reference in new issue
Block a user