From: "Morpheus" Newsgroups: comp.os.msdos.djgpp Subject: Re: compiling C++ Date: Mon, 8 Nov 1999 13:01:59 -0600 Organization: Zion Lines: 22 Message-ID: <8076na$los@hermes.acs.unt.edu> References: <7vsnag$jhc AT hermes DOT acs DOT unt DOT edu> <7vugut$7d9 AT hermes DOT acs DOT unt DOT edu> <3822ce3d DOT 0 AT news DOT uni-bielefeld DOT de> <7vuqnq$9nq AT hermes DOT acs DOT unt DOT edu> <38232437 DOT 0 AT news DOT uni-bielefeld DOT de> <804vqg$kfe AT hermes DOT acs DOT unt DOT edu> <38268138 DOT 0 AT news DOT uni-bielefeld DOT de> NNTP-Posting-Host: dfw-premium-23.dialup.unt.edu X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > But I still don't understand the output of gcc that you posted and that didn't show any error messages. Interesting. It seems a combination of a few things. First, I keep getting syntax errors for my first '#include' statement if it's the very first thing in the file. So, I stuck a comment in there like ' // '. The next problem was that my text-editor, WinEdit, was using the carriage return for the end-of-line character, which is not properly recognized by either Windows or UNIX as an EOL character. Consequently, my entire file was read as a single line begun by a comment. So, nothing was compiled. =) Funny. I checked it out on DOS and UNIX; both did the same thing. I was very perplexed. Now I just have to go correct my errors due to my being out of practice with C++. Too bad I don't have a java-to-exe compiler for UNIX. =) morpheus Email: hall AT cs DOT unt DOT edu Web: http://people.unt.edu/~dahall "You'll tell yourself, 'I don't believe in any of this fake crap!'"