What about C, C# and Lua for computers?
I recommend that you set a consistent input/output format for entries.
In TI-BASIC, are we allowed to display the characters in the decoded text one per line? Can we take input in Ans?
In Python, is a function valid?
In both caregories, are we allowed to exit with an error after printing the correct output?
In TI-BASIC, are we allowed to display the characters in the decoded text one per line? Can we take input in Ans?
In Python, is a function valid?
In both caregories, are we allowed to exit with an error after printing the correct output?
Muessigb wrote:
What about C, C# and Lua for computers?
C is considered C++ for the purposes of this contest. Do you actually want to submit C# and Lua entries?
lirtosiast wrote:
I recommend that you set a consistent input/output format for entries.
In TI-BASIC, are we allowed to display the characters in the decoded text one per line? Can we take input in Ans?
The convention I've seen so far is input via Input, output via Disp or Output. I'd recommend using that.
In TI-BASIC, are we allowed to display the characters in the decoded text one per line? Can we take input in Ans?
Quote:
In Python, is a function valid?
Something like input() and print would be best.
Quote:
In both caregories, are we allowed to exit with an error after printing the correct output?
No. Programs that generate errors, crashes, and exceptions will be counted the same as programs that do not correctly decode test input. 
KermMartian wrote:
Muessigb wrote:
What about C, C# and Lua for computers?
C is considered C++ for the purposes of this contest. Do you actually want to submit C# and Lua entries?
Yes, I was actually thinking about using either C, C# or Lua.
Quote:
Programs that generate errors, crashes, and exceptions will be counted the same as programs that do not correctly decode test input.
Does "test input" mean the example, or do you have additional test cases?
lirtosiast wrote:
Quote:
Programs that generate errors, crashes, and exceptions will be counted the same as programs that do not correctly decode test input.
Does "test input" mean the example, or do you have additional test cases?
I am interested in participating in this competition, but I have a few questions. How will I know if I have solved the cipher, is it a classic cipher e.g. Caesar, or Vigenere? Also, do I understand correctly that 68k calc's are not allowed for this challenge?
sub5 wrote:
I am interested in participating in this competition, but I have a few questions. How will I know if I have solved the cipher, is it a classic cipher e.g. Caesar, or Vigenere?
You'll recogniez recognize the plaintext if you successfully decode it. Quote:
Also, do I understand correctly that 68k calc's are not allowed for this challenge?
That's correct. Unfortunately, it's a logistical issue: not all of the judges have 68k calculators. KermMartian wrote:
The convention I've seen so far is input via Input, output via Disp or Output. I'd recommend using that.
Ans does seem easiest for the calc languages, especially for assembly, so for that reason I used it for each entry
Snektron wrote:
How is the encrypted message inputted? Just a variable inside the program?
Either via Input or whatever, or in Ans.
And how is the calculator source code size judged? (is the vat header included like in the caclulator's memory menu?)
The size of the program would be that in the Memory Menuy - 9 - length_of_program_name. So if my program is prgmA and the Memory Menu says 78, it would be 78-9-1=68.
I'm happy to announce that another Tuesday is upon us, so Challenge 2 of Cemetech Contest #15 is also here! If you haven't completed Challenge 1 yet, you still have time, and the only thing you'll lose is the (up to) 5 bonus points you get by submitting your solutions quickly. Challenge 2 adds a few additional rules that we learned from seeing how people worked with Challenge 1:
Challenge 2: VPUOUGHUVYUOOSIUWOPSTTEPMRWNSEOBHMYGUYUVUGP
Good luck!
- For Challenges 2 and 3, TI-BASIC, Axe, and Assembly programs should take the ciphertext in Ans and return the decoded plaintext in Ans as well.
- For Challenges 2 and 3, computer programs should take input from stdin and return output to stdout.
- If there are any constants or keys that affect how a particular cipher works (for example, the offset in a Caesar cipher), these should be defined in a modifiable way in the source, so that someone with the source code could change those constants without needing to modify anything else in the program.
Challenge 2: VPUOUGHUVYUOOSIUWOPSTTEPMRWNSEOBHMYGUYUVUGP
Good luck!
jonbush wrote:
If you haven't figured out Challenge 2 yet, here's a hint:
%26
I'm Kerm Martian and I approve of this message. %26
Good luck, everyone. I notice we haven't quite gotten as many entries as for the first challenge, so I hope everyone who is stuck on this one (or forgot to enter so far this week) will redouble their efforts. Register to Join the Conversation
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Advertisement