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

Pages: 1-

I dreamed a program - /prog/ contest 235871

Name: Anonymous 2012-06-02 1:45

So nonsense, EVERYONE that was in my dream turned to me and  "HAAA?!"'d before I woke up because it was cold and I wanted to pee.

-> The Program must have a GUI, depicting # ZHIMN and  # DHAN. What are they? From what I could figure out, they are two random data inside a treeview element. They can be anything, for example, two different environment variables caught by chance in execution time.

What does the program do?

Relate these two data with hipsters.


Yes, that's what I dreamed. There must be an ENTERPRISE purpose behind that.
===============================================================
Send your projects until: 11 of June of 2012.

Name: Anonymous 2012-06-02 1:47

This is a great example of why knowing how to spell doesn't imply you're not a retard.

Name: !L33tUKZj5I 2012-06-02 3:18

The Program must have a GUI,
Stopped reading there.

Name: Anonymous 2012-06-02 3:21

>>3
Were you serious when you said you think ,,GC is shit'', or were you just imitating the shitposter?

Name: VIPPER 2012-06-02 4:41

>>4
Perhaps, he is the shitposter.
It could be anyone, even you.
Dont trust anyone.

Name: Anonymous 2012-06-02 8:04

>>5
Perhaps, he is the shitposter.
Nah, I hold him to better standards.

Dont trust anyone.
Take your pills, ``please''.

Name: !L33tUKZj5I 2012-06-02 12:46

>>4
Were you serious when you said you think ,,GC is shit''

I suppose for some quick and dirty programs it's OK, but anything serious you should managed the memory yourself.

Name: Anonymous 2012-06-02 15:26

GUI

Name: Anonymous 2012-06-02 21:01

>>7
but anything serious you should managed the memory yourself.
Most objects are incredibly small and don't need to be reclaimed right away (leaving aside the fact that escape analysis can schedule deallocations optimally).  Really, the only moment you should do manual memory management is to free massive objects as quickly as possible when you're done with them.  For every free() you put in your code, you waste a few bytes of machine code that can never be reclaimed.

Name: Anonymous 2012-06-03 0:32

Here's a thought: if you're building large objects only to destroy (free) them a short time later, your program is probably inefficient.

Name: Anonymous 2012-06-03 0:45

>>10
That implies that every single database server in existence is inefficient.  Which isn't exactly wrong.

Name: Anonymous 2012-06-03 11:30

gc is not optimal. static structures always outperform both malloc amd gc.

Name: Anonymous 2012-06-03 13:29

What the fuck is this thread even about?

Name: Anonymous 2012-06-03 16:42

>>13
how do you like /prog/ so far?

Name: Anonymous 2012-06-03 17:00

>>13
GameCube.

Name: Anonymous 2012-06-05 0:28

Well, I saw a GUI in my dream. That's why it should have one.

But some of you want an EASYMODO? OK.

You can use ncurses or build your stuff in pure ASCII joy

Name: Anonymous 2012-06-05 5:51

>>1
oh my, i was borned on 11.06, is this a coincidence?!

Name: Anonymous 2012-06-05 10:16

>>17
i was borned

Name: Anonymous 2012-06-05 14:40

>>18
Me too

Name: Anonymous 2012-06-07 1:32

I was bourned again

Name: Anonymous 2012-06-07 14:38

>>20
I boned your mother

Name: Anonymous 2012-06-07 18:17

>>21
This is a pretty magical thing

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