Xref: news2.mv.net comp.os.msdos.djgpp:8383
From: "Maan M. Hamze" <mmhamze AT mail DOT utexas DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Turbo C++ query: thanks for help: sorry re off-topic-ness
Date: 6 Sep 1996 14:08:43 GMT
Organization: University of Texas at Austin
Lines: 32
Message-ID: <01bb9bfc$d52bc520$72fb5380@maan-m.-hamze>
References: <4395F66E9D AT fs2 DOT mt DOT umist DOT ac DOT uk>
NNTP-Posting-Host: slip-58-2.ots.utexas.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

A.Appleyard <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk> wrote in article
<4395F66E9D AT fs2 DOT mt DOT umist DOT ac DOT uk>...

>   I have a copy of Turbo C++ version 4.5, and found that to (run programs
that

I did not notice this before, but are you sure it is Turbo C++ ver 4.5? 
Anyway, beside the point!

>   With BC450RTL.DLL in the other computer's C:\WINDOWS\, my Windows
program
> worked OK. But having to copy a file into Windows is another thing for
the
> user to do and discourages portability of whatever Windows program I
write.

You really are making a big deal of this issue in my opinion.  This is a
run time module that is designed to keep the size of programs small without
the need to reinvent the wheel whenever you work on a program.  And ____It
is a part of the final product____ that you want to distribute.  This is
NOT an issue of portability.  This is an issue of distribution.  This DLL
and the EXE are both part of the program that you create.  DLL's are
everywhere:  bwcdll.dll, and the visual basic run time dll's (vbx100,
vbx200 etc...).  Your mistake is that you are thinking that a finished
product is and must be ONE EXE.  Look around you.  This is not the case. 
In addition to the EXE there are many many support files that comes with a
program.
M
-- 
Maan M. Hamze
mmhamze AT mail DOT utexas DOT edu
http://leb.net/~mmhamze