irc-compo 1. history :)

Hello All! By the way, this is last year’s compo. There were only 2 of them :-) === Cut === #Z80 Coders Compo ====================================== On IRC channel #Z80 for the last month Several coding mini-compos were held. Conditions of the competition very simple: the winner is the one whose procedure turns out to be the most fast. Only a few days were allotted to complete the task. The first components were organized by Mac_Buster/Extreme, information support - PHtb0t, of course with the assistance ppl with #Z80 :) The first compo was held from March 16 to 20 and was test. However, the results were made public. Despite the health of Mac Buster, who celebrated birthday. :) The following is a free translation information from the site http://z80.home.ml.org ... !!!!!!!! THANK TO ALL WHO HAVE CONTRIBUTED IN THIS COMPO!!!!!!!! The #Z80 IRC channel test compo (03/16/98 - 03/20/98) fast results v 1.5 -------------------------------------------------- Place | Nick | t-states -------------------------------------------------- 1st | Depredator/PHT | 49 -------------------------------------------------- 2nd | Sanchez/Ramsoft | 47 | Glip | 47 | StarSoft | 47| Busy Soft & Hard | 56* --------------------------------------------------- 3rd | www | 49 | Hacker Scorpion | 65 | Cja | 67* --------------------------------------------------- outdated | Strider | 47 | Falco | 49 * pixel2attr - read below >>> Stop! Was this a package for the fastest procedure or what? Why was first place given in 49 bars? <<< Well what can I say? It actually looks very strange. But there are reasons for this. This is the first component, and how It is known that I am not a professional compo organizer, but the rules competition had some gaps. Many participants asked I can see how fast their procedure is, and after the bummer they started screaming: "Wait! I'll do better! Don't count the procedure already sent!" And Deprederator was not one of them - his letter arrived first with a 49-cycle procedure before he started asking about her speed. Therefore, I decided to award him 1st place. And please don't ask me how fast your procedure compared to others! I won't say anything at all by any means! >>> 56 bars in 2nd place? Yes, you are a jokester! It's slower than the procedure in 3rd place!<<< Yes! But most of you have done procedures for recalculation familiarity into an attribute, and only Busy and Cja recalculated the pixel into attribute. And these are more flexible procedures. Busy did it faster and I gave him 2nd place. >>> About the results of Cja. You may ask: “It doesn’t seem Is it too slow?" <<< No, it doesn’t seem like it. Cja hasn't coded on Speccy for 2 years! >>> I see you are very smart in evaluating other people's procedures! Show me some of your own!!! <<< Hehe! Since I am in charge of the project, I decided not to take part in this competition at the time you send me your procedures and I I have the opportunity to see them. And some might say that I'm spying and can use some ideas from your procedures. But! My procedure was the first and had 47 bars! See compo history section. >>> Future compo <<< It all depends on your activity, and if you want to continue (with more interesting and more defined rules) write me /Mac_Buster@usa.net/ and indicate "Yes! I am participating in the following compo" >>> History of compo <<< I decided to make this compo because it's not very interesting to be on channel and just look at nicks without any interest in the conversation. The 1st compo was completed in just 1 hour! And I started and finished my procedurein almost 35 minutes including recruitment and testing time, but others who agreed to participate, asked for more time and the compo continued "a little" longer. We had to wait for quite a few more participants, who did not complete their work by the specified time. In short, it was not a compo, but a “soap opera”! Next compo complete second per second. >>> Special thanks <<< Thank you to all those who decided to take part! Whichever place are you didn't take it! I am infinitely grateful to Glip! Because he showed me that the Busy procedure is not char2attr, but pix2attr! Thank you for reading all this in my terrible english (From Ars: and I apologize for the translation :)) I am Russian and english takes 3rd month among all the languages that I know: 1.Russian 2.Assembler 3.English 4.C++/C-- 5.... === Cut === I was with you Ars^FTL