diff --git a/faq.html b/faq.html index 438363caf..23400c002 100644 --- a/faq.html +++ b/faq.html @@ -893,127 +893,6 @@ for more up to date information on downloading, compiling, and related FAQ infor Jump to: top
  • -
    -

    Q: Is there a way to not have to re-enter the same information, when making a change to my submission?

    -
    -

    Yes! The mkiocccentry(1) tool has some options to help write OR read from an -answers file so you do not have to input the author(s) or the submission -details (like the abstract, summary etc.), just to change a file.

    -

    To write to answers.txt try:

    -
        mkiocccentry -a answers.txt ...
    -

    Alternatively, if you wish to overwrite a file, you can use the -A -flag with the same option argument. Be very careful that you do not accidentally -overwrite your prog.c or some other important file!

    -

    To make use of the answers file, use the -i answers option like:

    -
        mkiocccentry -i answers.txt ...
    -
  • -
  • -
    -

    Q: What types of entries have been frequently submitted to the IOCCC?

    -
    -

    There are types of entries that are frequently submitted to the IOCCC. -While we do not wish to prevent people from sending -a submission to the IOCCC on a frequently submitted theme, -we do wish to provide a fair warning to those who do.

    -

    Fair warnings on frequently submitted themes:

    -

    IMPORTANT HINT: It is not fatal to send in those types of -entries, it is just HARDER to win with such a submission. A -submission on a frequently submitted theme will have to do something -in a really unique AND interesting way to even make it into the -final judging rounds. It will have to compete with previous IOCCC -winners based on the same theme.

    -

    IMPORTANT HINT: If you really wish send in a submission on a -frequently submitted theme, be sure that it is obfuscated in several -new and novel ways.

    -

    IMPORTANT HINT: Be sure to clearly explain near the beginning -of your remarks.md file, see the -FAQ on “remarks.md”, -why you are submitting an entry based on a frequently -submitted theme and how compares with previous IOCCC winners -of the same theme.

    -

    Examples of frequently submitted themes

    -
    Maze generator
    - -
    Tic-Tac-Toe/Noughts and Crosses/Xs and Os game
    - -
    Solitaire/Othello game
    - - - -
    Self-reproducing program
    - -
    Entries that just print “Hello, world!”
    - -
    Entries that use some complex state machine/table to print something
    - -
    ROT13
    - -
    pi or e computation
    - -

    The above list of frequently submitted themes is not exhaustive

    -

    Some final thoughts on frequently used themes

    -

    While it is possible to win a new IOCCC with one of these -frequently submitted types of entries, level of the competition from -previous IOCCC entries make it more challenging to be successful.

    -

    It is also important to note that the guidelines often -state something along the lines of:

    -
        We tend to dislike programs that: are similar to previous winning entries.
    -

    FAIR WARNING: Be sure to clearly explain near the beginning -of your remarks.md file, see the -FAQ on “remarks.md”, -why you are submitting an entry based on a frequently -submitted theme and how compares with previous IOCCC winners -of the same theme.

    -

    Jump to: top

    -
  • -
  • Q: What should I put in my submission Makefile?

    @@ -1041,52 +920,6 @@ command that is compatible with GNU Make version 3.81.

    Jump to: top

  • -
    -

    Q: May I use a different source or compiled filename than prog.c or prog?

    -
    -

    While your entry’s source filename, as submitted, must be prog.c, your entry’s Makefile -may copy prog.c to a different filename as part of the compiling/building process. For example:

    -
        # Makefile continues above ...
    -
    -    all: desired_name
    -
    -    desired_name: desired_name.c
    -            rm -f $@
    -            cc desired_name.c -o $@
    -
    -    desired_name.c: prog.c
    -            rm -f $@
    -            cp -f prog.c $@
    -
    -    clean:
    -            rm -f desired_name.o
    -
    -    clobber: clean
    -            rm -f desired_name.c desired_name
    -
    -    # Makefile continues below ...
    -

    We recommend that the make clobber rule remove files that your entry -creates as part of the compiling/building process.

    -

    You may also copy the compiled prog into a different file as part of compiling process. -For example:

    -
        # Makefile continues above ...
    -
    -    all: desired_name
    -
    -    different_name: prog
    -            rm -f $@
    -            cp -f prog $@
    -
    -    clean:
    -            rm -f prog.o
    -
    -    clobber: clean
    -            rm -f desired_name
    -
    -    # Makefile continues below ...
    -

    Jump to: top

    -
  • -
  • @@ -1172,37 +1005,6 @@ others are wondering about as well!

    See also the FAQ on “rules, guidelines, tools feedback”.

    Jump to: top

    -
    -
    -

    - What are the IOCCC best practices for using markdown?

    -
    -
    -

    The IOCCC makes extensive use of markdown. -For example, we submitting to the IOCCC, we have people -to submit remarks about entry in markdown format. Every -winning IOCCC entry uses a README.md markdown file -as the basis for forming the index.html web page for that entry. -All generated HTML pages on the Official IOCCC website -start with some markdown content.

    -

    IMPORTANT: Please read the IOCCC markdown best practices guide -as it lists things you should not use in markdown files.

    -

    See the markdown syntax guide. -See also CommonMark Spec.

    -

    Jump to: top

    -
  • -
  • -
    -

    Q: How do I report bugs in an mkiocccentry tool?

    -
    -

    As the mkiocccentry toolkit is -crucial in the contest, both for submitters and the judges, if you find a bug -(or you think you find a bug) we would be grateful if you were to report it at -the mkiocccentry issues -page.

    -

    Please see the -FAQ on “reporting bugs and other issues in the mkiocccentry repo” -in the mkiocccentry repo.

    -

    Jump to: top

  • @@ -1998,10 +1800,108 @@ submission manually then you would be violating

    Section 1: Entering the IOCCC: more help and details

    +Jump to: top +
  • +
    +

    Q: Is there a way to not have to re-enter the same information, when making a change to my submission?

    +
    +

    Yes! The mkiocccentry(1) tool has some options to help write OR read from an +answers file so you do not have to input the author(s) or the submission +details (like the abstract, summary etc.), just to change a file.

    +

    To write to answers.txt try:

    +
        mkiocccentry -a answers.txt ...
    +

    Alternatively, if you wish to overwrite a file, you can use the -A +flag with the same option argument. Be very careful that you do not accidentally +overwrite your prog.c or some other important file!

    +

    To make use of the answers file, use the -i answers option like:

    +
        mkiocccentry -i answers.txt ...
    +

    Jump to: top

    +
  • +
  • +
    +

    Q: May I use a different source or compiled filename than prog.c or prog?

    +
    +

    While your entry’s source filename, as submitted, must be prog.c, your entry’s Makefile +may copy prog.c to a different filename as part of the compiling/building process. For example:

    +
        # Makefile continues above ...
    +
    +    all: desired_name
    +
    +    desired_name: desired_name.c
    +            rm -f $@
    +            cc desired_name.c -o $@
    +
    +    desired_name.c: prog.c
    +            rm -f $@
    +            cp -f prog.c $@
    +
    +    clean:
    +            rm -f desired_name.o
    +
    +    clobber: clean
    +            rm -f desired_name.c desired_name
    +
    +    # Makefile continues below ...
    +

    We recommend that the make clobber rule remove files that your entry +creates as part of the compiling/building process.

    +

    You may also copy the compiled prog into a different file as part of compiling process. +For example:

    +
        # Makefile continues above ...
    +
    +    all: desired_name
    +
    +    different_name: prog
    +            rm -f $@
    +            cp -f prog $@
    +
    +    clean:
    +            rm -f prog.o
    +
    +    clobber: clean
    +            rm -f desired_name
    +
    +    # Makefile continues below ...
    +

    Jump to: top

    +
  • +
  • +
    +
    +

    Q: What are the IOCCC best practices for using markdown?

    +
    +
    +

    The IOCCC makes extensive use of markdown. +For example, we submitting to the IOCCC, we have people +to submit remarks about entry in markdown format. Every +winning IOCCC entry uses a README.md markdown file +as the basis for forming the index.html web page for that entry. +All generated HTML pages on the Official IOCCC website +start with some markdown content.

    +

    IMPORTANT: Please read the IOCCC markdown best practices guide +as it lists things you should not use in markdown files.

    +

    See the markdown syntax guide. +See also CommonMark Spec.

    +

    Jump to: top

    +
  • +
  • +
    +

    Q: How do I report bugs in an mkiocccentry tool?

    +
    +

    As the mkiocccentry toolkit is +crucial in the contest, both for submitters and the judges, if you find a bug +(or you think you find a bug) we would be grateful if you were to report it at +the mkiocccentry issues +page.

    +

    Please see the +FAQ on “reporting bugs and other issues in the mkiocccentry repo” +in the mkiocccentry repo.

    +

    Jump to: top

    +
  • + +