mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Change 'tri-graphs' to 'trigraphs' - it's one word

Browse Source 
The is a file excluded from this commit that has had the change because
there are other changes but the file is incomplete. That file will be
committed when the fixes are complete which will happen at a later date.
This commit is contained in:
Cody Boone Ferguson committed 2023-06-05 05:52:57 -07:00
1 parent c64d9c86a2
commit 7dbb9fc2fe
22 files changed
+43 -43
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

1991/rules.txt
+2 -2
View File
@@ -195,7 +195,7 @@ POINTS TO PONDER:
each entry is judged when we:
* look at the original source
* If it is ANSI, convert tri-graphs to ASCII
* If it is ANSI, convert trigraphs to ASCII
* C pre-process the source ignoring '#include' '#define' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -216,7 +216,7 @@ POINTS TO PONDER:
(it is ok only if you warn us in the 'remark' header item)
* won't compile under both BSD or SYS V Un*x
* use an excessively long compile line to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are similar to previous losers :-)
1992/guidelines.txt
+2 -2
View File
@@ -53,7 +53,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* If it is ANSI, convert tri-graphs to ASCII
* If it is ANSI, convert trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -143,7 +143,7 @@ OUR LIKES AND DISLIKES:
(it is ok only if you warn us in the 'remark' header item)
* won't compile under both BSD or SYS V Un*x
* abusing the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
1993/guidelines.txt
+2 -2
View File
@@ -47,7 +47,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -168,7 +168,7 @@ OUR LIKES AND DISLIKES:
(it is ok only if you warn us in the 'remark' header item)
* won't compile under both BSD or SYS V Un*x
* abusing the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
1994/guidelines.txt
+2 -2
View File
@@ -60,7 +60,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -180,7 +180,7 @@ OUR LIKES AND DISLIKES:
(it is ok only if you warn us in the 'remark' header item)
* won't compile under both BSD or SYS V like Un*x systems |
* abusing the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
1995/guidelines.txt
+2 -2
View File
@@ -59,7 +59,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -181,7 +181,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most |
most POSIX P1003.1/P1003.2 like systems |
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
1996/guidelines.txt
+2 -2
View File
@@ -56,7 +56,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -188,7 +188,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
1998/guidelines.txt
+2 -2
View File
@@ -73,7 +73,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -207,7 +207,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
2000/guidelines.txt
+2 -2
View File
@@ -43,7 +43,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -177,7 +177,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
2000/rince/README.md
+1 -1
View File
@@ -236,7 +236,7 @@ common tricks. Taken through the standard rounds listed in the
space saved by using a single long string constant is more than
outweighed by the ability to further obfuscate.
2. convert ANSI tri-graphs to ASCII
2. convert ANSI trigraphs to ASCII
These are not used.
2001/guidelines.txt
+2 -2
View File
@@ -43,7 +43,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -176,7 +176,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
2004/guidelines.txt
+2 -2
View File
@@ -45,7 +45,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -178,7 +178,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
2005/guidelines.txt
+2 -2
View File
@@ -48,7 +48,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -181,7 +181,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
2006/guidelines.txt
+2 -2
View File
@@ -48,7 +48,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -184,7 +184,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
2011/guidelines.txt
+2 -2
View File
@@ -50,7 +50,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -200,7 +200,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
2012/guidelines.txt
+2 -2
View File
@@ -83,7 +83,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -230,7 +230,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are similar to previous winners
* are identical to previous losers :-)
2013/guidelines.txt
+2 -2
View File
@@ -87,7 +87,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -279,7 +279,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
| * are "blob-ier" than they need to be
| * are too similar to previous winners :-(
2014/guidelines.txt
+2 -2
View File
@@ -84,7 +84,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -278,7 +278,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are "blob-ier" than they need to be
| * are rather similar to previous winners :-(
2015/guidelines.txt
+2 -2
View File
@@ -100,7 +100,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -319,7 +319,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are "blob-ier" than they need to be
* are rather similar to previous winners :-(
2018/guidelines.txt
+2 -2
View File
@@ -106,7 +106,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -357,7 +357,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are "blob-ier" than they need to be
* are rather similar to previous winners :-(
2019/diels-grabsch1/guidelines.txt
+2 -2
View File
@@ -108,7 +108,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -359,7 +359,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are "blob-ier" than they need to be
* are rather similar to previous winners :-(
2019/guidelines.txt
+2 -2
View File
@@ -108,7 +108,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -359,7 +359,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are "blob-ier" than they need to be
* are rather similar to previous winners :-(
2020/guidelines.txt
+2 -2
View File
@@ -109,7 +109,7 @@ HINTS AND SUGGESTIONS:
a number of tests to an entry:
* look at the original source
* convert ANSI tri-graphs to ASCII
* convert ANSI trigraphs to ASCII
* C pre-process the source ignoring '#include' lines
* C pre-process the source ignoring '#define' and '#include' lines
* run it through a C beautifier
@@ -376,7 +376,7 @@ OUR LIKES AND DISLIKES:
* depend on a utility or application not normally found on most
most POSIX P1003.1/P1003.2 like systems
* abuse the build file to get around the size limit
* obfuscate by excessive use of ANSI tri-graphs
* obfuscate by excessive use of ANSI trigraphs
* are longer than they need to be
* are "blob-ier" than they need to be
* are rather similar to previous winners :-(