| |
| |
| |
|
Comments:
<0> nite
<1> sleep well
<2> I'm creating a library and I was thinking that I could release it without a header file so that you could incorporate it into your project simply doing #include "mylib.c" in the module/file which is using it
<2> does that sound like a crazy idea or is there acturly a tradition for doing that?
<2> the library just has 6 or 7 functions, prefixed with a 3 letter id, so there shouldn't be any conflicts
<2> naming conflicts
<3> .c files inclusion is ugly.
<3> Also, your library users will have to care that it's included only once
<3> etc. etc.
<2> ok
<2> isn't an included .c file only visible to the .c file in which it was included?
<2> hmm that's where my C knowlege ends... :)
<2> I like that you don't have to change your compile command line when including a .c file
<4> n8
<5> good morning...
<6> moin
<7> allo.
<8> moin
<5> if you are so insisting on 'moin', I accept moin :)
<6> denk: that's what i thought a couple of years ago :)
<9> hi!
<1> rotfl
<1> never seen this quit-msg before
<10> which one?
<9> "Ping timeout"?
<11> without the quotes
<12> i would have guessed operation not permitted.
<11> its some socket error
<10> Toobeees :)
<13> ehlo
<14> http://www.nag.ru/2006/1210/img/ugas/002.jpg
<5> old
<5> see also 001-007
<15> hehe
<16> Hello!
<16> Could you speak your mind abot my code at http://fatcat.ftj.agh.edu.pl/~kfsz/oneway4.c?
<17> apart from the ****ed up coding style?
<16> sorry
<16> do you have any advice?
<16> for me?
<18> it thought it was "Krakow", not "Crackow"
<18> um, is there any problems with your program ?
<16> what should syntax of malloc look like?
<6> void* malloc(size_t)
<16> could you look whether it is correct now, please?
<16> maide: I'm afraid your modification returns syntax error before "void"
<9> oh my! this style is truly ****ed up!
<16> what can you recommend me?
<16> is sinus funcion represented by sin(x) in math.h?
<13> evening
<0> hello
<1> yo
<5> solaris question: ld called from make(1) does not link a program, but the same ld called from gmake(1) on the same host links fine
<5> where am I wrong?
<6> kfsz: what do you mean by "syntax" then?
<19> denk: "gmake" usually is GNU make, whereas "make" is some funny solaris thingy which is /almost/ a real "make" program
<6> kfsz: that's the prototype for malloc
<6> denk: well, how does ld get called from make(1)?
<5> maide: I still don't know it, I don't have solaris at this time...
<5> I wanted to see it under truss
<6> denk: just a second. how would you know that ld fails to link your program then?
<19> denk: usually you're using some feature gnu make has, but solaris make hasn't
<5> Myaw-Myaw: wake up!
<5> show the error
<20> ld -L/usr/local/lib -I/usr/local/include -lm -lsocket -lnsl -lpcap
<20> oh, wrong buffer
<6> well, that looks incomplete
<20> socket /var/tmp//ccIk67LV.o
<20> shutdown /var/tmp//ccIk67LV.o
<20> ld: fatal: Symbol referencing errors. No output written to a.out
<20> collect2: ld returned 1 exit status
<6> well
<6> you need -lsocket
<0> just for my info, what kind of platform is that (that you need -lsocket I mean)?
<6> solaris
<20> sunos 10
<0> hmmkay
<6> myaw: add -lsocket and see if that's enough, or if there are more unresolved symbols
<0> he has -lsocket already :)
<0> michai.flags &= ~USELESS_COMMENT;
<6> :P
<21> Un Grosso Saluto a Tutto Il Canale < #c >
<6> thanks jv
<10> haven't seen that in a long time :)
<20> sorry, i was not here
<13> suppose we need the good old *!*Simpson@* ban back :)
<6> jv: join #openbsd, and you'll see a lot of it :P
<6> myaw: any further problems? or does -lsocket solve your issue
<6> ?
<5> maide: I will show you the problem next week
<5> because solaris is at my home
<5> and Myaw-Myaw is busy now
<6> alright :)
<20> i hate oracle >8/
<5> it hates you too :)
<0> bye
<20> maide: thanks, it seems so
<22> Myaw-Myaw, denk heya
<6> myaw: very well then
<0> bye
Return to
#c
or
Go to some related
logs:
#worldchat
sei un fango
#worldchat
#worldchat
nvidia-glx for xorg 7.0 ubuntu
#london
#worldchat
#worldchat
#worldchat
#london
|
|
