Fun challenge submission for 2025/ncw2.

[antoine-mathys]

Fun challenge submission for 2025/ncw2.

[lcn2]

Hello @antoine-mathys ,

We plan on accepting your solution to the fun challenge.

We are in the process of changing how we present and announce fun challenges and present winning entries.

Please do us a favor and create a GitHub repo with your source code solution to some repo of your own.

We will create a pointer to the repo. Feel free to create a README.md for that repo that describes your solution as you wish. Your repo needs to carry the entire ww.ioccc.org infrastructure, just a handy Makefile. That repo's README.md can describe how someone might wish to compile and run your announce fun solution.

We are creating a new 2025/challenge.html web page that will credit you for being the first to solve the fun challenge for 2025/XYZZY. We will add a link to your GitHub repo with your solution.

Once you give us the URL to your solution repo, we will create the 2025/challenge.html web page and point to it.

REQUEST

In a comment below, @psymar, please give us the URL of your solution repo.

[antoine-mathys]

Hello @lcn2 ,

That's good.

I strictly followed the instructions on https://www.ioccc.org/faq.html#pull_request.
As indicated, I created the repository https://github.com/antoine-mathys/winner and the branch 2025-ncw2-fun-challenge-1.

It seems that you want me to create a new repository. If that is true, I would gladly do it. However, I suggest that you update the instructions given in the descriptions of the fun challenges to point to an equally detailed step-by-step guide. I don't understand git and would never succeed otherwise.

Cheers,

[lcn2]

Hello @lcn2 ,

That's good.

I strictly followed the instructions on https://www.ioccc.org/faq.html#pull_request. As indicated, I created the repository https://github.com/antoine-mathys/winner and the branch 2025-ncw2-fun-challenge-1.

It seems that you want me to create a new repository. If that is true, I would gladly do it. However, I suggest that you update the instructions given in the descriptions of the fun challenges to point to an equally detailed step-by-step guide. I don't understand git and would never succeed otherwise.

Cheers,

We plan to do so, and @xexyl has kindly offered to write a FAQ soon on what to do.

But first, we need to generate the 2025/challenge.html page (via a 2025/challenge.md page, which in turn will be initialized by a tool we plan to use when forming a new year's set of winning entries).

So give us a bit of time to set this all up. We will keep you posted.

UPDATE 0

As can example, see:

https://github.com/psymar/IOCCC-dogon-2025-fun-challenge-2

Feel free to use the 2025/ncw2 tarball to modify with your code.

You can just provide a better prog.c if you wish.

[xexyl]

Hello @lcn2 ,

That's good.

I strictly followed the instructions on https://www.ioccc.org/faq.html#pull_request.

As indicated, I created the repository https://github.com/antoine-mathys/winner and the branch 2025-ncw2-fun-challenge-1.

It seems that you want me to create a new repository. If that is true, I would gladly do it. However, I suggest that you update the instructions given in the descriptions of the fun challenges to point to an equally detailed step-by-step guide. I don't understand git and would never succeed otherwise.

Cheers,

As I wrote that (and many others) FAQ entries I actually already had in mind to make a new FAQ entry after this has been created.

I would be happy to hear your feedback to make it more helpful if necessary.

And well done here!

[xexyl]

Hello @lcn2 ,

That's good.

I strictly followed the instructions on https://www.ioccc.org/faq.html#pull_request. As indicated, I created the repository https://github.com/antoine-mathys/winner and the branch 2025-ncw2-fun-challenge-1.

It seems that you want me to create a new repository. If that is true, I would gladly do it. However, I suggest that you update the instructions given in the descriptions of the fun challenges to point to an equally detailed step-by-step guide. I don't understand git and would never succeed otherwise.

Cheers,

We plan to do so, and @xexyl has kindly offered to write a FAQ soon on what to do.

It does seem like the right thing to do 😀

(Although I would have been happy to do so anyway.)

I also would GLADLY take feedback from others to make it as useful as possible. In fact I rather hope others can provide feedback!