The W2K crash proggy
-
I've seen it at least a dozen times around here... everyone's using
#include "stdio.h"
in that proggy. Why? I think it should be
#include <stdio.h>
Yeah, I know, both ways work, but the really correct version should be the one with the wakas™, not the tickies™. Bestow thy knowledge upon me, C++ gurus. A list is only as strong as its weakest link. - Don Knuth
-
I've seen it at least a dozen times around here... everyone's using
#include "stdio.h"
in that proggy. Why? I think it should be
#include <stdio.h>
Yeah, I know, both ways work, but the really correct version should be the one with the wakas™, not the tickies™. Bestow thy knowledge upon me, C++ gurus. A list is only as strong as its weakest link. - Don Knuth
I don't think it matters. The compiler will look ONLY in the system include directory if the include is between the <> symbols. If you put quotes around it instead it will look in the system inlcude directory FIRST, then go to the user specified include directories for the search. As long as the standard file is found, who cares. Brigg Thorp Software Engineer Timex Corporation
-
I've seen it at least a dozen times around here... everyone's using
#include "stdio.h"
in that proggy. Why? I think it should be
#include <stdio.h>
Yeah, I know, both ways work, but the really correct version should be the one with the wakas™, not the tickies™. Bestow thy knowledge upon me, C++ gurus. A list is only as strong as its weakest link. - Don Knuth
maybe eveybody has their own custom version of stdio.h ? like, i prefer to define size_t as __int64 instead of whatever stupid type MS thinks it should be. :) -c
Smaller Animals Software, Inc. http://www.smalleranimals.com
-
I don't think it matters. The compiler will look ONLY in the system include directory if the include is between the <> symbols. If you put quotes around it instead it will look in the system inlcude directory FIRST, then go to the user specified include directories for the search. As long as the standard file is found, who cares. Brigg Thorp Software Engineer Timex Corporation
Yes I know. I mentioned that in my post. I just wanted to test out a silly new gradient filter I found. A list is only as strong as its weakest link. - Don Knuth
-
I've seen it at least a dozen times around here... everyone's using
#include "stdio.h"
in that proggy. Why? I think it should be
#include <stdio.h>
Yeah, I know, both ways work, but the really correct version should be the one with the wakas™, not the tickies™. Bestow thy knowledge upon me, C++ gurus. A list is only as strong as its weakest link. - Don Knuth
oooh - nice gradient ;) cheers, Chris Maunder (CodeProject)
-
oooh - nice gradient ;) cheers, Chris Maunder (CodeProject)
Funnily enough that's the first thing I thought when I clicked on the post, but I thought I'd avoid appearing easily taken and keep schtum ;P. What I'm not gonna admit is that I then went across to an article, and found another post with a <pre> in just to see whether you'd made it standard across the site or if it was the poster who'd done it :-D. BTW the scrolly things in code listings in articles didn't go amiss - nice idea, I'd no idea it was even possible. Mucho HTML catch-up research needed soon methinks. Ok, off to bed, it's 0227 here and WAY too late for 'us youngens' (as you over 30's would say ;P), like my grand self, to be hangin' round in the Salloon (sic?) :). -- Andrew.