| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Comments:
<0> OT: http://mizar.lod.com/~n/primegraf.tar
<0> OT: had to whip up a makefile
<0> the X11 routines aren't that great, just enough to open a window and draw what i need
<1> omg. i don't have x11 installed on here.
<0> ah
<1> hrm.. i'll have to look at it later. i don't want to hunt for my developer cd to install the x11 package.
<0> yeah cool
<0> it does the first 640000 numbers
<1> you should make screenshots. xwd is your find.
<1> s/find/friend
<0> OT: heh, check this out. i was designing X fonts in C:
<0> #define X 1,
<0> #define _ 0,
<0> int shape[10][10] =
<0> {
<0> { X X X _ _ _ _ _ _ _ },
<0> { _ X X _ _ _ _ _ _ _ },
<0> { _ X X _ X X X X _ _ },
<0> { _ X X X X X X X X _ },
<0> { _ X X X _ _ _ X X _ },
<0> { _ X X _ _ _ _ X X _ },
<0> { X X X _ _ _ _ X X X }
<0> };
<2> niv_, no libX11
<3> hmm
<2> what should I link it too
<0> heh
<2> !!!
<3> could look like swastika if you move it around
<2> niv_, no libX11
<2> what should I link it too
<0> it's an h
<1> please don't flood:P
<4> in the episode "Bodyswap", Cat plays the word jozxyqk in a game of Scrabble, claiming it to be a cat word meaning 'the sound you make when you get your ***ual organs trapped in something'.
<0> yeah sorry
<0> =/
<0> jeffloc: needs libX11
<1> niv_, i usually use bdf fonts. they are easy to parse and x11 comes with gobs of them.
<1> niv_, why didn't you just use xbm or xpm format? :P
<0> OT: ah.. i was only using Xlib's pixel drawing capabilities, so i designed my own
<0> OT: i'm not much of an X programmer, i know only the basics
<0> of Xlib
<5> http://orangetide.com/temp/bdf.c and http://orangetide.com/temp/bdf.h .. free parser for bdf files
<5> (just in case you don't want to use the built-in font stuff in x11)
<0> ah nice
<6> ****, does this sprintf function need to NOT follow the documentation
<6> ;/
<6> needs*
<7> ?
<0> damn OT
<0> we need to teach you to put more spaces in your code
<0> ret=make_font(256);
<0> i'd write: ret = make_font(256);
<0> that **** gets hard to read after a while hehe
<6> niv_ spaces, what's this?
<6> buf[0][i++]='\0',strncpy(&buf[1][1],buf[0],strlen(buf[0])+1),targetp=strstr(&buf[1][1],"GET");
<6> it's enough
<6> ;)
<0> hehe
<8> niv_: no, you just don't know how to read.
<6> no need for spaces
<6> ;)
<0> whitespace is your friend
<9> I have headache =/
<0> hey aedinius
<8> I_v0: what's wrong with that code?
<1> niv_, why would you put all those spaces in there? what purpose does it serve?
<6> so... can anyone tell me why sprintf doesn't follow the documentation? :)
<6> evilgeek nothing
<10> it does. you are a kook.
<0> OT: whitespace just makes it enormously easier for me to read.
<1> = looks so different for letters and numbers that you can visually see the difference.
<8> I_v0: how doesn't it?
<1> when i write out formulas on paper i don't put spaces between things either. nobody does
<6> evilgeek niv_ was only wondering about white spaces
<0> OT: I usually follow the 4.3 BSD C coding style
<1> niv_, feel free to pump it through gnu indent.
<6> evilgeek oh you are takling about sprintf?
<4> erm wow, I'm getting 30k/sec from a torrent that's several years old
<1> niv_, i tend to be a cross between K&R and linux style. unless i'm writing code for an existing project, then i follow thier conventions.
<0> OT: When I write my own code, I will write in K&R alot, although that's changing lately because I'm getting used to writing in C89/C99 at work.
<1> i don't mean i use K&R prototypes.
<1> i mean i just use few spaces and put { on the same line as things
<0> Alot of our code is still C78, but they want all new code in C89 I think
<1> zid_, amazing.
<4> if(){
<6> evilgeek well, suppose we want from some place in memory 4 bytes which would be HEAD... oh I know, sprintf put's a '\0' at end
<6> that's the case ;)
<0> you put { on the same line after function declarations?
<9> I do
<0> function decls are the only place i ddon't put { on the same line
<1> zid_, well if(foo==x) { .. so i guess i still stick a lot of unnecessary spaces in there. just not enough unnecessary spaces for niv_
<6> niv_ I also often put } in the same line with while statement or for
<6> ;)
<1> niv_, about half the time i put them on the same line for function declarations. i haven't decided which way i like.
<4> lemme make some test code just for you guys
<1> honestly i don't really believe in formatting code. 1. there are programs that can reformat 2. i can read code just fine even if it's all on the same line, but sometimes debuggers are easier to use if you break stuff up onto multiple lines.
<6> OrngeTide one is for sure, it's faster to ommit whitespaces
<6> ;)
<1> it saves wear and tear on your spacebar
<11> I'd rather not be forced to horizontally scroll to look at code.
<0> OT: I'd get killed at work if I didnt format my code nicely
<4> http://rafb.net/paste/results/uQ7Lpv41.html <-- my style
<1> i just tell people to "quit whining, you big baby" usually in emails Cc'd to everyone.
<9> My laptop has widescreen. I don't have to scroll horiz.
<0> OT: Although when I whip up a quick test program to do something I'm libel to not care about the formatting, of course
<12> I checked in a bunch of code where I do foo() { \n } as opposed to foo() \n { \n }
<9> niv, liable, not libel
<6> OrageTide yeah, looking at that that the spacebar is most oftenly pressed key it's prolly a good idea to save it for IRC for ex.
<6> ;)
<12> and people at work went nuts
<0> aedinius: thanks
<4> niv: wot about mine?
<9> niv, sorry, nitpicky
<0> zid: lemme look
<9> Sometimes.
<1> i've had bossed come to me and tell me their developers are late because my code wasn't formatted nicely. and i tell them they are trying to cover up the real reason they are late and he should figure out what that reason is and quit p***ing the buck.
<0> i'd at least put a space between int main(int argc, char **argv) and {
<0> if not a line
<4> I hate(
<4> this,
<0> and for the other blocks, put a space
<4> ****,
<4> }
<1> aedinius, funny. i pronounce liable as libel.
<4> lie-able
<1> Wazm, people need to not be big babies. that's what i keep telling everyone. :P
<4> niv, I didn't use **argv god damnit
<9> OrngeTide: Says you
<0> zid: sorrry, that's what I use
<1> zid_, the a is silent in my dialect.
<4> I think it's uglier
<9> OrngeTide: Now the rest of us have to deal with your HIDEOUS HORRIBLE BADLY FORMATTED CODE
<4> dilect*
<1> i prounouce dialect as di-lect too
<4> s*
<1> aedinius, yes. and i'm okay with with that.
<9> =]
<1> zid_, dilect is not a word:P
<0> no, i didn't mean int main( \n int argc, \n char **argv) \n }, i meant int main(int argc, char **argv) \n {
<4> who thinks my style is just teh leet?
<12> OrngeTide: but aren't you from a state where people talk kind of funny?
<4> I hate them both :P
<9> I don't care, as long as people's code is 1) consistent 2) readable
<1> Wazm, i'm from the midwest. we think everyone else talks funny. :P
<4> I'm perfectly capable of seeing that an if lines up with an } without needing the { on it's own line
<0> zid: not on it's own line, that's only for functions
<1> i have a bit of a "great lakes dialect". whatever that means. mostly we just talk fast and drop like every other syllable.
Return to
#c
or
Go to some related
logs:
I fucked my mother in the ass
#microsoft
vbs logical and
#online
#hardware
#politics
#flash
cannot run project unless a host application
OTBB Quotes
#unixhelp
|
|