| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | TIC |
BL> and sort it like this... BL> qsort(*LIST, n, sizeof(LIST[0], sort); BL> Terrific! Why do I put *LIST? What the hell does *that* mean? BL> LIST PE> That doesn't mean anything that I am aware of. Just "LIST" by PE> itself is what you want in that code. &LIST would probaly also PE> work, but only because the "&" should be ignored. I suspect PE> that the "*" is being ignored by your compiler. I would have PE> expected a syntax error. That's what *I* expected. But it needs *LIST or (void *)LIST. This is the one thing that *really* gives me the shits with C. In Pascal, if the syntax is not clear you just try a few things and see what the compiler reckons. In C, the compiler thinks everything is great. You have to run it and even then it can work. What I have to do is awful things under Windows, and see if the bloody thing locks up! And even *then* I am not sure if it's right! Oddly, the best way to fuck it is put in lots of printf()s with odd format strings. If something odd happens, I cna usually lock it by whacking in printf()s all over the place, and then sort out where it's going stupid by removing them one at a time. BL> And work out a way to copy/move/erase files in UNIX. Or not. I BL> suppose UNIX does files? PE> Posix does directories, yes. BFN. Paul. I like "UNIX" better than Posix. I get this image of programmers in a Chinese brothel surrounded by eunuchs. "Posix" just doesn't have a good image. ___ Blue Wave/QWK v2.12 @EOT: ---* Origin: Precision Nonsense, Sydney (3:711/934.12) SEEN-BY: 711/934 712/610 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.