Search results

Okay, I'm not a REAL programmer (I know java, js, you know, fluff languages), but I did read K&R's "C" book way back when. my question is, why are actual UNIX C programs out there so hard to read and compile? i guess it is because of the fact that they were written to compile on like a billion...

you can also look in one of the linux HOW-TOs on www.linux.org. like http://www.linux.org/docs/ldp/howto/Tips-HOWTO.html that one has examples of piping together commands and stuff. although its linux, there are still a lot of similarities btwn OS X and linux. also, when i was learning...

After using Mozilla for a few more hours and trying out the tab feature, I am hooked. IE is now banished from the dock. But I still can't type URLs into that little text box. When I do, nothing happens. It was like that with NS6.2 as well. It just started happening one day. IE5.1 lets me...

I think I'm gonna make a switch to Mozilla from IE. I read about Mozilla in Time today, but was skeptical, because I've used NS6.2 before, and the experience stank. But Time had glowing things to say about Mozilla's speed, and being a non-geek publication, I felt those words had to mean...

Are you using the Carbon version of tetex, complete with the dvi viewer and everything? Are you able to compile your TeX code? I'm using it with no problems... :confused:

Cool, just the answer I wanted. I will go try this at home ASAP. :D

Hi. I have a G4 350MHz with OS X 10.1.3, and for some reason, the network connection through my cable modem no longer works. My question is, how does one trouble shoot problems like this? I seem to remember when I ran Linux a long long time ago, there were utilities that checked stuff like...

Check /Developer/Documentation/DeveloperTools/Compiler directory for documentation. file://localhost/Developer/Documentation/DeveloperTools/Compiler/Compiler.d.html#pgfId=5068 This one has docs on #include paths