Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!psuvax1!psuvm!uh2
From: UH2@psuvm.psu.edu (Lee Sailer)
Newsgroups: comp.lang.c++
Subject: Re: Borland C++ binary header files
Message-ID: <91164.112014UH2@psuvm.psu.edu>
Date: 13 Jun 91 15:20:14 GMT
References: <1991Jun5.220703.662@helios.physics.utoronto.ca>
 <1991Jun6.224738.28002@donner.SanDiego.NCR.COM>
Organization: Penn State University
Lines: 13

I use them too, and they help a lot.  However, I did get caught by what
Borland admitted is a bug.  I trimmed everything down to a 10 line
program that compiled without errors, but produced onerous run time
errors, when the binary include feature is turned on.  They've
promised to let me know when they figure it out, but it's been a couple
of weeks, now.

The main symptom was that the values of argc and argv were not correctly
passed to main().  They both had values of NULL.  When binary includes
is turned off, it works normally.  The problem has to be somewhere in
my includes, I guess, but Borland cannot find it (they say).

                                                            lee