-----------------------------------

Mackie

Sun Apr 20, 2008 9:15 pm


To fork or not to fork.

-----------------------------------

I have to decide whether or not to use my Color Selector as a procedure, which will halt all other operations while it executes, or to fork a process, but everyone says that's bad because of the randomness of it all. I don't really see any problems with forking it so far. Any suggestions?

I still need to optimize. And rename some stuff. Just to let everyone know that I am aware.


-----------------------------------

syntax_error

Sun Apr 20, 2008 9:26 pm


RE:To fork or not to fork.

-----------------------------------

im sure you can find a way around, "forking" 

I say : not.


-----------------------------------

LaZ3R

Sun Apr 20, 2008 9:49 pm


RE:To fork or not to fork.

-----------------------------------

I'll say no as well. It's a nice program by the way :)

Fork should only be used for music. If you make turing do two things at once aside from playing a music file on top of processing data, you end up asking for trouble :)

I don't see your program doing anything wacky itself while it's running, however, I still think if you can avoid forking anything, try it out instead :)


-----------------------------------

Mackie

Sun Apr 20, 2008 9:59 pm


RE:To fork or not to fork.

-----------------------------------

Thanks, for the input. I just don't see any good reason not to fork yet. The only way I could think of integrating it with the main loop would be to make it a class. Which veers away from my original concept of a one line call. If anyone has an idea of how I could accomplish this while still keeping it a procedure, please share. :-)

Also, I hear that the preview gradients don't work on some computers, if they don't, please speak up.

Thanks again.


-----------------------------------

LaZ3R

Mon Apr 21, 2008 8:40 pm


RE:To fork or not to fork.

-----------------------------------

They show up fine here :) Very nice job I must say :)