Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

weekly programming contest

Name: Anonymous 2009-12-21 17:24

so i thought since /prog/ is filled right now with non programming related bullcrap. how about we discuss about a official weekly /prog/ programming contest. we could make one each week. we could discuss a debate on the subject 2 days before the assignment.

it would really increase quality posts and programming related subjects, and add some posts here because it seems a bit lame here. also the nonprograming related bullshit i think might exsist because of boredom and we all know how bad boredom is.

discuss. NOW!!!

Name: Anonymous 2009-12-21 17:35

We had one of these a while back. I'd find the thread but I have no goat.

This week's task: Make a program that takes another program's source as input and decides whether, for a given finite input to the program, if the program will halt or not, without compiling+running the program.

Name: Anonymous 2009-12-21 17:41

>>2
That's easy as fuck. Just tell me how much memory the machine has (RAM + HDD + hardware registers + mechanical states + expansion/external such as other networked machines or the Internet if it's connected to it).

Name: Anonymous 2009-12-21 17:47

another game?

Name: Anonymous 2009-12-21 18:01

I still like the factorial fobonacci tetris idea.

Name: Anonymous 2009-12-21 18:03

Challenge: write a C++ parser

Name: Anonymous 2009-12-21 18:03

While I am always in favour of actual coding threads, I have several concerns.
1. Like the `game ideas' threads, these contest idea threads end up being all talk and no walk. If you have a contest idea post it and see if it takes off.
2. If give something a week timeline, it will be forgotten. People will procrastinate and never actually code up a solution, or the thread will leave the front page with half a dozen posts. A shorter timeline is more likely to work.

Name: Anonymous 2009-12-21 18:03

>>5
* fibonacci
I feel kind of bad about it :(

Name: Anonymous 2009-12-21 18:26

>>7
hmm i thought a week was fine because you had alot of time and could always make a new thread each week on the same day.

im sorry im uncreative as fuck, aint got shit ideas.

Name: Anonymous 2009-12-21 18:33

>>6
That's NP Complete

Name: Anonymous 2009-12-21 18:35

These challenges should be doable in at least half a day's work or less. If you think the problem you proposed ca be done in that timeframe, but other's don't think so, you should post some demo code to prove it.

Name: Anonymous 2009-12-21 18:42

Possible challenge idea:
Write a simple compiler(to bytecode) for a toy language(imperative or functional, no ABC or Brainfuck toy compilers please. Subsets of real languages allowed.) of your choice. To simplify or avoid lexing/parsing tasks altogether, one is allowed to use Lispy syntax(this isn't a requirement, but would simplify the task somewhat).

Name: Anonymous 2009-12-21 18:43

*compiling to C/ASM or other languages allowed too.

Name: Anonymous 2009-12-21 20:20

Challenge: POKe/prog/ BATTLE!

Simulate a single pokemon battle between two trainers. No Items, each trainer has only one Pokemon. Each Poke/prog/ has the following stats:

Speed: Determines which Poke/prog/ attacks first
Attack: % to increase damage
Accuracy: % to hit with abilities
Dodge: % to avoid getting hit
Defense: % to reduce damage taken
Health: Amount of damage that may be taken before KO

And 4 Abilities that may be used during combat.

Name: Anonymous 2009-12-21 20:41

>>14
You forgot the part where it must be done in BBCode? Back to /v/.

Name: Anonymous 2009-12-21 21:51

Challenge: Print 1000 Sussmans.

Name: Anonymous 2009-12-21 22:05

>>16
(loop repeat 1000 do (print "Sussman"))

Name: Anonymous 2009-12-21 22:07

>>17
What do?

Name: Anonymous 2009-12-21 22:09

>>18
It's just LOOP syntax for running arbitrary forms.
Here's another one (dotimes (i 1000) (format t "Sussman~&"))

Name: Anonymous 2009-12-21 22:31

>>17
loop repeat do
And they say Java is verbose.

Name: Anonymous 2009-12-21 22:36

>>20
Nobody is forcing you to use LOOP, however you're right, I find my Lisp code to be somewhat verbose, since I tend to give my symbols long descriptive names (which is not a problem as long as there's auto-complete), so I could read them at a later date without wondering what I meant. Of course, if you really use statements like that often, and dotimes isn't good enough, you could always write a macro which looks like (repeat 1000 (print "Sussman")) if you wanted (it would only take 2-3 lines of code tops at that). Does Java give you as many options to avoid verbosity if you so desire?

Name: >>21 2009-12-21 22:39

(defmacro repeat (times &body body) `(dotimes (,(gensym) ,times) ,@body))

Name: Anonymous 2009-12-22 0:40

>>22
Right, that's so much more readable than
for (int i=0; i<1000; ++i) { ; }

Name: Anonymous 2009-12-22 0:50

>>23
Apples and Oranges. >>22 is a macro for his repeat construct show in >>21. If you were to make a C macro for your post you could have accidental variable capture.

Name: Anonymous 2009-12-22 2:34

You mean FIBONACCI PONG-TRIS?
I never got around to doing that one. Now that I have 2 weeks of vacation on my hands, I might just give it another shot, though.

Name: Anonymous 2009-12-22 2:59

>>12
Whose bytecode? Can we make one?

Name: Anonymous 2009-12-22 9:20

>>24
If you were to make a C macro for your post you could have accidental variable capture.
Hahaha. Like anyone programming in the C family thinks farther than #DEFINE COPY_AND_PASTE_PROGRAMMING 1.

Name: Anonymous 2009-12-22 11:17

Suggestions:

- Tetris (or Pongtris or whatever variation you want)
- A C Compiler
- sagebot

Name: Anonymous 2009-12-22 11:33

>>28
write me some Loeb.

Name: Anonymous 2009-12-22 11:39

ramming in the C family thinks farther than #DEFINE COPY_AND_PASTE_PROGRAMMING 1.

Name: Anonymous 2009-12-22 21:12

>>26
You can make your own, but you should provide at least a minimal interpreter, so we could test it. Otherwise, you're free to pick some bytecode out there that already have interpreters/compilers/JIT(s) written for them, as long as we can test them out ourselves.

Name: Anonymous 2009-12-22 21:50

>>31
I say people should be implementing random esolangs.

Name: Anonymous 2010-11-14 23:08

<

Name: Anonymous 2013-01-18 22:51

/prog/ will be spammed continuously until further notice. we apologize for any inconvenience this may cause.

Don't change these.
Name: Email:
Entire Thread Thread List