BC++ 3.0 wierd compiler bug? or me?

Article View: comp.os.msdos.programmer

Article #896

Back to comp.os.msdos.programmer Previous Next

#896

From: Holographic Banana
Date: Thu, 13 Aug 1992 23:12

20 lines
877 bytes

This is really bizzare --

In Borland C++ v3.0 I'm passing a bunch of const char * and char *. The
parameters comming that are giving me wierd results are constant strings,
e.g.

foo("blah");

What is happening is that in the call to foo(),  I get a pointer to a
terminating '\0', i.e. the compiler is treating my calls the same as

foo("");

Has anyone experienced this and have found a remedy???
I'm running DOS 5.0, and compiling with overlays, C++, huge memory model,
fastest code, standard stack frame for debugging.

Thanks, 

James

Technical Details

Message-ID: <1992Aug13.171217.58139@cc.usu.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!caen!hellgate.utah.edu!cc.usu.edu!slb1b

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!caen!hellgate.utah.edu!cc.usu.edu!slb1b
From: slb1b@cc.usu.edu (Holographic Banana)
Newsgroups: comp.os.msdos.programmer
Subject: BC++ 3.0 wierd compiler bug? or me?
Message-ID: <1992Aug13.171217.58139@cc.usu.edu>
Date: 13 Aug 92 17:12:17 MDT
Organization: Utah State University
Lines: 22