| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9
Comments:
<0> all your indentation is totally scrwed
<1> that is a socket buffer I wrote a while back so I wouldn't have to keep building new buffers for simple text
<0> and you need to clean up your usages of comma
<2> I hadn't actually seen the code. Ow! This is messy
<0> make lines shorter
<0> and insert spaces around ops
<0> and split into short functions
<3> ok
<3> going to work then
<0> the good idea is to introduct the function process()
<3> _reppir thanks for that code
<0> that accepts connected socket
<1> also, I recommend you initialize all variables when you create them
<2> Organize the code in a way that makes it flexible, preferably readable and maintenable as well
<1> I_v0: that code can be usable, but it is well commented and I hope it helps
<2> Hrm, don't initialize variables uselessly
<0> I_v0: the big mistake is, you don't clean up the zombie child provcesses
<3> DynaMish I will look at fork() once again in Programming in C, thought exit(0), or return would be enough
<2> I think you would benefit from gaining some programming experience with simpler stuff
<0> THis is code for cleaning zombie child processes: http://rafb.net/paste/results/5J5kxf21.html
<3> ok thanks guys
<3> going to work
<1> I learned how to program from writing IRC bots
<4> MOSCOW, Russia (Reuters) -- Vladimir Putin's decision to stop a small boy as he walked through the Kremlin and kiss his stomach was prompted by a desire to "touch him like a kitten," the Russian president said on Thursday.
<5> if i want to use the thread safe version of errno, do i define _REENTRANT or _LIBC_REENTRANT?
<1> is that standardized?
<1> I don't see it in the man pages or in the errno.h
<1> bits/errno.h does refer to _LIBC_REENTRANT, on a fedora box
<3> _reppir I just breifly red what you gaved me, as you write there reading is inefficient
<3> you cite there
<1> Im not following
<5> yea.... i see _LIBC_REENTRANT... but.... when i google #define _REENTRANT errno, it says thats the correct #define to use
<5> so... i'm kinda lost
<6> how can I start OpenGL and return from OpenGL from within gtk_main() without getting a segmentation fault? I have a button which does some opengl-stuff, the opengl-stuff works fine but when I kill opengl the program receives a segfault
<5> not sure which to use
<3> _reppir http://rafb.net/paste/results/ANgMvD51.html
<1> majikman: could it hurt to use both?
<3> a while ago you gaved me this
<5> no... i just want to know definitively
<1> majikman: sorry, don't know
<5> its ok, thanks
<1> I_v0: yes, what are your comments?
<3> _reppir the same as yours, it's an inefficient way with sockets, additionaly no timeout can be given, so one can open at most 65536 connections
<3> thus stunning the machine
<1> you mean in reference to the code I posted?
<3> _reppir yes, you are cite W. Richard Stevens
<3> without are*
<1> hehe yes
<3> ;-)
<1> that code was meant to give an example of socket buffering, not I/O :)
<1> you draw good points though
<3> broken my code up, now looking at cleaning after fork()
<3> then I'll present what I've got ;)
<1> nice, RSS feeds for video driver updates
<3> _reppir consider this
<3> http://rafb.net/paste/results/0o8wGK61.html
<3> now it compiles correctly with -Wall -O0 -g
<7> considered
<3> and gdb doesn't complain
<3> pkrumins :)
<7> oh.
<1> looks like youre reading char by char
<3> mhm
<1> you should move the child code into a separate function
<1> main() is entirely too long
<1> and it's tough to tell what structure the } is closing
<8> what the **** kind of advice is that?
<8> the only problem with that code is the weird indentation, and it's clear what that } closes.
<3> evilgeek I use vim
<7> its 8 space identation :P
<3> on 19' LCD it appears corretcly
<3> :)
<8> pkrumins: but it's inconsistent. look at the for loop starting on line 81.
<3> evilgeek good point, it should end earlier
<7> whats wrong at L81?
<3> pkrumins this loop should end earlier
<7> oh ja
<7> L81
<7> its all fukd up
<3> pkrumins no it isn't
<3> ;>
<7> well first char is not fukd up
<7> rest is
<3> why?
<7> sorry, just joking
<3> wrrr
<3> :)
<8> why should the loop end earlier? that changes the semantics of the program.
<1> it's good practice to write readable code
<3> evilgeek it should end at line 94
<3> for loop only handles getting all of the chars
<7> I suggest you read Writing Solid Code
<3> pkrumins ok
<7> MS Press - Writing Solid Code - Microsoft's Techniques for Developing Bug-Free C-Programs - 1993
<9> Microsoft's techniques?
<9> hahahahahaha
<9> hahahha
<3> buehehehehe
<9> hahaha
<7> It's a very good book.
<3> pkrumins no thanks
<3> ;)
<7> It's just stupid that you laugh.
<9> pkrumins: Maybe Microsoft's employees should read it. :-)
<7> Do you know Code Complete, then?
<3> <7> MS Press - Writing Solid Code - Microsoft's Techniques for Developing Bug-Free C-Programs - 1993
<3> ;>
<9> pkrumins: Yes, I haven't read it.
<7> go f* yourself, I_v0
<10> I_v0 APRIL FOOLS mother ****er
<2> Ahaha
<10> we all know microsoft and bug free don't mix
<10> :)
<9> 1993? That is the pinnacle of Microsoft's auditing dive.
<3> Darken- ;)
<9> pkrumins: Chill out dude. :-P
<10> microsoft has more bugs than a kambodian hooker living in a mud hut
<7> thats because developers are ignorat
<10> no
<10> THEIR developers are lazy and ignorant
<10> not all
<7> yes of course not all.
<7> i dont want to go into it, it's an excellent book
<9> Most developers are lazy and ignorant Darken-.
<7> same as code complete is
<11> on what do you base that opinion?
<10> it must be a corporate policy to slack when you develop MS products
<10> Samy, not the old school ones
<10> only the new school I bought a degree from India I can't use a computer I'm a programmer
<9> Darken-: Especially the old school ones.
<10> programmers
<10> no
<7> The book covers why microsoft software is buggy btw (1993, excel product mainly)
<9> Darken-: Yes.
<10> you're insane
<11> things change
<10> there's products running for 20-30 years solid as a rock
<9> Darken-: Minority.
<10> those are =programmers=
<10> old school
<11> anyone know the name of a #c++ op?
<7> ZorbaTHut
<12> speaking of lazy and ignorant... hi Darken
<7> :)
<13> Wow. Check it out - http://www.w3counter.com/globalstats/
<7> Hehe, I like this question: what is a programming language?
<13> It shows Firefox (1.0 + 1.5) at 24%
<2> Linux at 1%? Hrm...
<2> This information seems unreliable
<13> Maloeran: Which information seems wrong to you?
Return to
#c
or
Go to some related
logs:
passdump hush-hush
#nhl
#computers
#politics
#beginner
winsmon.dll
#nhl
emachines crt blinking
#windows
#linux-noob
|
|