Jens Staal dixit: > ./a.out > 24
Good guess! > no idea if that is what we want... The code checks for == 22. I suppose I must change that into an offsetof check… should be safe, as offsetof is already used in the code. For now, make the “== NUM” into a “>= NUM”. > compiler(s)). The thing is, I have no idea who/how to fix the kernel/ape bug > responsible or who to get in touch with for that. Me neither… the Lucent people seem to be dead or, worse, working for Google on their “Issue 9” programming language now. The 9front people are out of question, and others… no idea – maybe cnuke@ (who should be damn well reading this mailing list ☺) could enlighten us. > I find it awesome with such a rapid feedback! If my rate of feedback is “rapid” even when I think I’m on a slow streak… I guess I’m doing good and shouldn’t pressurise myself just that much. Thanks! ☺ As for the job… Could be worse. I get paid for system administration, hacking PHP crap and dealing with Java™ Enterprise crap. No surprises I am pretty “done” in the evenings. But it lets me “play” enough, so it’s not half bad… and it does pay the bills, barely. bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in "Notes on Programming in C"
