@# Quotes DB     useful, funny, interesting





Google
 
Web www.quotesdb.info
Undernet  |  EFnet  |  Quakenet  |  Freenode  |  Dalnet  |  Ircnet  |  Galaxynet
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17



Comments:

<0> she doesn't know what's she's into..
<1> tsokolat: oh no. i sense he would have to carry her all the way. else i doubt she'll agree :-p
<0> no. no.. the getting married part
<1> oh.
<0> Ka-bar: make sure she doesn't bump her head..
<2> cheeksy, tsokolat, Falchion, Ka-bar ..
<1> Eric :o)
<0> Nanuq
<3> Nanuq of the North
<1> wiggly wiggly worm.
<4> now this lover666 is sending me msg's
<3> cheeksy: More like a snake, but who's counting? *ducks*
<1> no, such a teeny tiny word.



<1> worM.
<3> OH! I get it! It's like nicknames. You know, when you call a fat guy Slim or a guy with only a right arm Lefty. Got it!
<1> yeah, decided according to genetic looks and qualities.
<1> tsokolat
<1> psst
<5> which command is used to comapare files?
<2> MatrixEVT: diff
<6> vncviewer via command line works to my vnc server (vncviewer localhost:1), but Terminal Services Client fails with "error" to same local server. "error" - nothing descriptive
<7> this will be exicting
<7> it compiles, but if this actually works at first shot... Ill celebrate with a beer :P
<8> Jostein, you won't be getting drunk any time soon then :)
<7> heh
<7> well. multithreading may be PITA
<7> but I prefer to have the threading handled in the framework I use, instead of making tons of dirty multihreading hacks in the projects using this framework
<7> Im pretty sure we can agree on that?
<8> Yes :)
<7> good, good
<9> greetings starfighter...
<9> you have been recruited by the Star League to defend the frontier against Xur and the Ko-Dan armada
<10> lol
<7> #1: code cleaning up threads in the pool at exit doesnt account for itself being a thread :P
<8> Jostein, no beer for ya :)
<7> hell. multithreading poses a set of new challenges
<7> but so far it works surprisingly well
<7> in fact... only thing ****ing up so far is the cleanup code :P
<7> ****ing **** refuses to exit
<7> debugging MT stuff is sooo much fun :P
<11> ..so don't write buggy MT code :p
<7> jonesboy: ****er :P
<7> jonesboy: the code is fine. the cleanup code aint :P
<7> heh
<7> I -did- make on bad presumption so..
<7> Ill let you get away with that one
<7> having a thread clean up threads is simply bad design
<12> nah, thats what you get for trying to do it the easy way instead of the Java way ;-)
<13> anybody tried the aes_i586 module on SuSE?
<14> anyone care to help a linux newbee?
<7> my favorite one is "// **** happens" followed by "try {" :P
<11> if (ERROR_CONDITION) { exit(-1); }
<12> My code doesn't need error handleing since it doesn't have errors :-)
<11> we have an antique piece of AAA code that actually has that exact construct in it. it makes me feel all warm and fuzzy (and scared) inside.
<7> hehehe
<7> Lion-O: heh
<7> my "favorite" errorhandling code comes from the B worlds
<7> VB world
<7> "on error resume next"
<12> lol
<15> rofl



<12> try { stuff } catch(Exception e) { do more stuff }
<12> peons :)
<12> now I know why I usually do this stuff in Linux.
<11> int i=0; try_again: for (;i<10;i++) { try { stuff(); } catch(Exception e) { goto try_again; } }
<11> ;)
<12> HA HA HA
<11> elegant error handling using goto!
<12> I wonder what'll happen if I try to continue my bot development on Windows. hmmm, perhaps something to try later on.
<7> jonesboy: goto is bad. always :P
<11> Jostein: goto bigot!
<12> Newsted could play pretty good IMO.
<7> whats annoying is that the only thing ****ing up is the cleanup code
<12> lol
<12> Jostein: aah, I see you chose to go multi threading afterall? good choice IMO
<7> Lion-O: I realized Id have to write dirty MT hacks in the client-apps, if the framework wasn't inherently MTed to begin with
<7> Lion-O: Id rather handle threading in the framework, and make the clients cleaner
<12> absolutely.
<7> I just for the love of god figure out why this thing bugs
<12> buggy code :)
<12> Jostein: cool. I'll be sure to keep a hot cup of java coffee ready :)
<16> cleanup code that causes crashes usually means you sent the client or are still using **** that was p***ed by pointer...or reference...rather than copying
<7> safemode: point is... I check the thread pool. Its -empty-
<7> safemode: yet.. stil there seems to be 1 thread running
<7> I dont get it
<16> how do you know 1 thread is still running?
<7> because the app hangs there and doesnt exit
<7> ... well at least 1 thread
<16> perhaps your thread pool counter starts off at the wrong offset? did you try just starting at +1 to see if the cleanup code doesn't fail ?
<7> safemode: different than yours though
<16> when my app had exit issues, it wasn't due to threads, but to the call to kill being acted upon, but then destroyed before the other threads recieved it
<7> safemode: I first had the cleanup code as a thread of its own. bad idea.
<7> safemode: So Ive moved it to the main thread, to avoid any issues
<7> it runs.
<7> says everything is cool. and THEN the app should exit. but it doesnt
<7> I even inserted a graceperiod for leftover threads. to no effect
<16> you use locks?
<7> this code is as MT-safe as it can be
<16> how do you call for the death of the children threads? and
<16> and//
<7> every inter-thread communication is invoked
<7> safemode: htis aint C btw :P
<7> or C++
<16> well, it sounds like a cl***ic race
<7> yeah
<16> so something isn't MT safe
<7> well. it is -safe-. the app doesnt crash :P
<7> but damn if it will exit either
<16> perhaps it's just stuck in a loop
<16> you can check that if you use strace
<7> in fact only thing that doesnt work well is exiting. everything else works fine
<16> your main program is in control of exiting,so if it's stuck in a loop waiting for threads, this will be apparent with strace
<7> have a few ideas I'll look into
<16> asit will keep doing gettimeofday's and nothing else
<7> yeah
<7> touche this is C# and .NET-code
<7> heh
<16> blegh.. anyways good luck ..i'm off to shower
<7> thanks
<17> in case I've not said this yet today: _I hate moving._
<15> you have
<15> but understandable
<13> I get following error: ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel . What do I do wrong?
<15> something tells me the cipher isn't supported by the kernel
<11> I was gonna say: "that one doesn't explain itself to you?"


Name:

Comments:

Please enter the result of the sum 63 + 46 (to avoid spam):






Return to #linux
or
Go to some related logs:

#MissKitten
p5gd1-vm fire
EAGLE Chili Sauce
widcam
nordicmafia c++
td look firefox iexplorer
#MissKitten
im sick as a dog
coffeegirl
miss-kitten



Home  |  disclaimer  |  contact  |  submit quotes