31 is 9.
9 is 4.
4 is magic.
Rank | User | Size | Date | Code |
1 | Juju | 548-70%=164.4 | 9/23/2014 6:25:12 PM | Spoiler For Spoiler: |
Rank | User | Size | Date | Code |
1 | JWinslow23 | 360-70%=108 | 10/4/2014 9:37:27 AM | Spoiler For Spoiler: |
Rank | User | Size | Date | Code |
1 | Ivoah | 962-70%=288.6 | 9/26/2014 6:32:23 PM | Spoiler For Spoiler: |
Rank | User | Size | Date | Code |
1 | 3298 | 611-70%=183.3 | 10/4/2014 2:54:53 PM | Spoiler For Spoiler: |
2 | ben_g | 676-70%=202.8 | 9/28/2014 2:52:53 PM | Spoiler For Spoiler: |
Rank | User | Size | Date | Code |
1 | 3298 | 630-70%=189 | 10/4/2014 2:54:53 PM | Spoiler For Spoiler: |
2 | ben_g | 861-70%=258.3 | 10/3/2014 3:52:36 AM | Spoiler For Spoiler: |
Rank | User | Size | Date | Code |
1 | 3298 | 493.5-70%=148.05 | 10/4/2014 2:54:53 PM | Spoiler For Spoiler: |
Rank | Lang | User | Size | Date |
1 | Golfscript | JWinslow23 | 108 | 10/4/2014 9:37:27 AM |
2 | SysRPL | 3298 | 148.05 | 10/4/2014 2:54:53 PM |
3 | Ruby | Juju | 164.4 | 9/23/2014 6:25:12 PM |
4 | Java | 3298 | 183.3 | 10/4/2014 2:54:53 PM |
5 | C | 3298 | 189 | 10/4/2014 2:54:53 PM |
6 | Python | Ivoah | 288.6 | 9/26/2014 6:32:23 PM |
Yay, got it to 562-70%=168.6 characters in Ruby.1. No, input of 4 means instant input of "4 is magic".
EDIT: 559-70%=167.7 now. Also I have a few questions:
- Do I have to print "4 is 4" with an input of 4? (No would save a few bytes)
- "Ninety-nine" or "ninety nine"? Does it matter? (No would save one byte)
- Capital letter at the beginning? (No would save a few bytes)
You PM your code to JWinslow23.What he said ^^
I would like to congratulate you for keeping a contest alive for this long (11 contests in such short period of time even though you are not a staff member). I know on IRC you said there weren't many entries for this one but the thing is that normally mini-contests die after 3 or 4 of them because the novelty wears off after a while (and in this case, school started). In fact, some recent contests like the revival of cage matches and the music contest never actually got any entry, if they even started at all. So good job. Some future suggestions to perhaps bring people back if they stopped participating:Thank you for your kind remarks. I will try to use your suggestions.
-Put the contest theme inside the title (for example: Code Golf Contest #12: ThemeName)
-Perhaps do a small change of direction in terms of theme. Keep the same idea but explore themes that were not explored before
-Make the deadline 2 weeks for each contest if the regulars look busy
-Make sure that the rules are well planned for each contest (perhaps have somebody review them before the contest starts?) so that there are as few rule edits in the middle of the contest as possible and less loopholes. For example, for the olympic ring contest, the easiest way to win was to use HP PPL language.
Yep, what DJ said. Congrats for keeping it up for 11 iterations and getting many people to enter each time! I entered in every contest so far, and the ideas you gave for the next ones looks pretty interesting and challenging.I would like to congratulate you for keeping a contest alive for this long (11 contests in such short period of time even though you are not a staff member). I know on IRC you said there weren't many entries for this one but the thing is that normally mini-contests die after 3 or 4 of them because the novelty wears off after a while (and in this case, school started). In fact, some recent contests like the revival of cage matches and the music contest never actually got any entry, if they even started at all. So good job. Some future suggestions to perhaps bring people back if they stopped participating:Thank you for your kind remarks. I will try to use your suggestions.
-Put the contest theme inside the title (for example: Code Golf Contest #12: ThemeName)
-Perhaps do a small change of direction in terms of theme. Keep the same idea but explore themes that were not explored before
-Make the deadline 2 weeks for each contest if the regulars look busy
-Make sure that the rules are well planned for each contest (perhaps have somebody review them before the contest starts?) so that there are as few rule edits in the middle of the contest as possible and less loopholes. For example, for the olympic ring contest, the easiest way to win was to use HP PPL language.
In related news, the deadline of this contest is moved to October 5, and new contests will now be on Saturdays instead of Mondays.
As for new contests, here are the ones that are most likely to happen up until #15 (if I can squeeze another month or two out of this thing) (these are only ideas, not giving away every detail yet):
#12: Befunge Numbers (make optimal expressions in RPN that evaluate to input)
#13: A Picture's Worth 140 Characters (give a way to compress and decompress images into a 140 character or less string)
#14: Getting Out What You Don't Put In (output every character your program DOESN'T have, and nothing else)
#15: History Repeats Itself (make a program that, when repeated, outputs two different specified strings)
If you have any questions about these questions, contact me. I can try to clarify most of the details for you.
seven hundred three thousand four hundred fifty is 41
fourty-one is 9
nine is 4
four is magic
The aspects I'm not sure about are these:My output currently looks like this (for input 703450):1. No.Code: [Select]seven hundred three thousand four hundred fifty is 41
The aspects I'm not sure about are these:
fourty-one is 9
nine is 4
four is magic
- Do I need a period at the end? (2-6 additional bytes, depending on language, so not too bad)
- Is the correct number written out in letters, or should I mangle the other one instead, or both?
- Do I need an upper-case letter at the start of each line? (That would be a pain to do!)
- The spaces and dashes should not be counted, right?
Okay then, my SysRPL, Java and C entries are done. My fourth question was actually meant in a different way ("thirty-one" is 10 chars, but all the examples look like we shall count the 9 letters only), but your answer reminded me that the dash can be replaced by a space, simplifying my programs a little. Thanks for that. :)Forty. Fourteen.
By the way: "forty" or "fourty"? I hope the latter is acceptable (despite my spell-checker complaining about it ... English is not my first language) because the former would break my concept of reusing the same lookup table for 13-19 and 2x-9x, and "forteen" looks just wrong.