home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!stanford.edu!ames!kum.kaist.ac.kr!worak!usenet
- From: mjkim@kaist.ac.kr (Kim Myoung-Jun)
- Subject: Re: BC++ 3.1, outportb -> Bad call
- Message-ID: <1993Jan10.094545.17863@worak.kaist.ac.kr>
- Sender: usenet@worak.kaist.ac.kr (Usenet)
- Organization: Korea Advanced Institute of Science and Technology
- X-Newsreader: TIN [version 1.1 PL8]
- References: <1993Jan1.081040.46014@kuhub.cc.ukans.edu>
- Date: Sun, 10 Jan 93 09:45:45 GMT
- Lines: 10
-
- Turn off pre-compiled headers. I have simillar experience.
- Using BC++ 3.0 with pre-compiled headers on, it often produced
- incorrect EXE file with successful compilatoin message.
- I could fix this by Full Build.. (or deleting .SYM maybe works).
- Now I doesn't use pre-compiler headers. Yes, compling is slow.
- But it's not much time and I am happy with correct EXE file.
-
- Myoung-jun Kim
- mjkim@jupiter.kaist.ac.kr
-